CVE-2025-21629General(linux / linux_kernel)

LOWCVSS 5.5 · MEDIUM

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

In the Linux kernel, the following vulnerability has been resolved: net: reenable NETIF_F_IPV6_CSUM offload for BIG TCP packets The blamed commit disabled hardware offoad of IPv6 packets with extension headers on devices that advertise NETIF_F_IPV6_CSUM, based on the definition of that feature in skbuff.h: * * - %NETIF_F_IPV6_CSUM * - Driver (device) is only able to checksum plain * TCP or UDP packets over IPv6. These are specifically * unencapsulated packets of the form IPv6|TCP or * IPv6|UDP where the Next Header field in the IPv6 * header is either TCP or UDP. IPv6 extension headers * are not supported with this feature. This feature * cannot be set in features for a device with * NETIF_F_HW_CSUM also set. This feature is being * DEPRECATED (see below). The change causes skb_warn_bad_offload to fire for BIG TCP packets. [ 496.310233] WARNING: CPU: 13 PID: 23472 at net/core/dev.c:3129 skb_warn_bad_offload+0xc4/0xe0 [ 496.310297] ? skb_warn_bad_offload+0xc4/0xe0 [ 496.310300] skb_checksum_help+0x129/0x1f0 [ 496.310303] skb_csum_hwoffload_help+0x150/0x1b0 [ 496.310306] validate_xmit_skb+0x159/0x270 [ 496.310309] validate_xmit_skb_list+0x41/0x70 [ 496.310312] sch_direct_xmit+0x5c/0x250 [ 496.310317] __qdisc_run+0x388/0x620 BIG TCP introduced an IPV6_TLV_JUMBO IPv6 extension header to communicate packet length, as this is an IPv6 jumbogram. But, the feature is only enabled on devices that support BIG TCP TSO. The header is only present for PF_PACKET taps like tcpdump, and not transmitted by physical devices. For this specific case of extension headers that are not transmitted, return to the situation before the blamed commit and support hardware offload. ipv6_has_hopopt_jumbo() tests not only whether this header is present, but also that it is the only extension header before a terminal (L4) header.

0.0/ 10 priority

Sources & remediation

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • linux_kernel

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • Technical details provided in 1 signal
  • General: 1 classified signal
  • 1 total mentions across 1 day

Affected systems

Vendors
Products
linux_kernel

2 versions affected across 1 product

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-08-11: 1Technical Details · 2026-08-11: 108-11
Signal classification1 categories
General
1100.0%
Referenced assets1 URL
Full discourse1 post
  • Windows Forum@windowsforum
    General

    🛡️ CVE-2025-21629 isn’t a new Windows networking flaw—it’s an old Linux kernel bug wearing an NVD timestamp disguise. Care only if WSL 2, a VM, or container host runs vulnerable Linux. https://windowsforum.com/security-alerts.84/cve-2025-21629-affects-linux-kernels-not-windows-networking.442315/?utm_source=x&utm_medium=social&utm_campaign=news_node84 #LinuxKernel #Wsl2 #Cve202521629 #Ipv6Networking https://t.co/YZcD98tVcJ

    Post summary

    The tweet debunks a misconception that CVE‑2025‑21629 is a new Windows networking flaw, clarifying it is an older Linux kernel bug relevant only to WSL 2, VMs, or container hosts.

    0000060
    1.3K followersView on X
CPE platform detail9 entries

9 of 9 entries

PartVendorProductVersionTarget SWTarget HW
OSlinuxlinux_kernel---
OSlinuxlinux_kernel6.12--
OSlinuxlinux_kernel6.12--
OSlinuxlinux_kernel6.12--
OSlinuxlinux_kernel6.13--
OSlinuxlinux_kernel6.13--
OSlinuxlinux_kernel6.13--
OSlinuxlinux_kernel6.13--
OSlinuxlinux_kernel6.13--

Explore more