Vulnerability · Published Oct 18, 2026 · Assigned by Linux

CVE-2026-98829wifi: mac80211: drop oversized fragments to avoid extra_len overflow

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 6% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 94.1% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: drop oversized fragments to avoid extra_len overflow In ieee80211_rx_h_defragment(), fragment payloads are accumulated into entry->extra_len as subsequent fragments arrive: entry->extra_len += rx->skb->len; When the final fragment arrives, the head fragment is dequeued, and pskb_expand_head() is called with entry->extra_len to ensure sufficient tailroom for all queued fragments before copying: if (skb_tailroom(rx->skb) < entry->extra_len) { if (unlikely(pskb_expand_head(rx->skb, 0, entry->extra_len, GFP_ATOMIC))) { ... } } while ((skb = __skb_dequeue(&entry->skb_list))) { skb_put_data(rx->skb, skb->data, skb->len); dev_kfree_skb(skb); } In commit 69f132236827 ("mac80211: shrink struct ieee80211_fragment_entry"), entry->extra_len was narrowed from unsigned int to u16 in order to reduce structure memory footprint. However, an IEEE 802.11 frame sequence can contain up to 16 fragments (frag numbers 0..15). If a sequence of large fragments arrives (e.g. from a malicious peer or rogue AP), the sum of fragment lengths can exceed 65535 bytes (for example, 15 fragments of 4400 bytes total 66000 bytes). Because extra_len is a u16, this addition overflows and wraps around modulo 65536 (e.g. 66000 wraps to 464). Consequently, pskb_expand_head() allocates only the truncated amount of tailroom (or is skipped entirely if the head fragment already has >= 464 bytes of tailroom). When skb_put_data() subsequently iterates through the queued skb list, it appends the full payload into the undersized buffer, causing skb_put() to trigger skb_over_panic() and crash the kernel in softirq context. A legitimate MSDU in IEEE 802.11 is at most 2304 bytes (or up to 7935/11454 bytes for A-MSDU, which is not fragmented), well below U16_MAX. Fix this without increasing the size of struct ieee80211_fragment_entry by checking whether adding the incoming fragment length would exceed U16_MAX. If so, purge the queued fragments and drop the frame. [assign a separate drop reason]

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-98829
Debian:13linuxno fix listedDEBIAN-CVE-2026-98829
Debian:14linux7.2.10-1DEBIAN-CVE-2026-98829
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-98829
Ubuntu:26.04:LTSlinuxno fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-98829
Ubuntu:26.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-aws-7.0no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-98829
Ubuntu:26.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-azure-7.0no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-98829
Ubuntu:26.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-azure-fde-7.0no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-98829
Ubuntu:26.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-gcp-7.0no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-98829
Ubuntu:26.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-hwe-7.0no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-98829
Ubuntu:26.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-98829
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-nvidia-7.0no fix listedUBUNTU-CVE-2026-98829
Ubuntu:26.04:LTSlinux-nvidia-bosno fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-98829
Ubuntu:26.04:LTSlinux-oem-7.0no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-98829
Ubuntu:26.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-oracle-7.0no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-98829
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-98829
Ubuntu:26.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-98829
Ubuntu:26.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-riscv-7.0no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-98829
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-98829
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-98829

Affected products (as reported)

VendorProductVersions
Linux Linux 69f132236827ce7d4531846cc2b9447dd5620aff – before 9338b2dea74cb0fc80a4c958b68e687610ba226169f132236827ce7d4531846cc2b9447dd5620aff – before 870b8cb9baa9bd859deceb33ae158011e6ba236069f132236827ce7d4531846cc2b9447dd5620aff – before 5e4f3509793b4db2c0835340224743db680e861f
Linux Linux 4.3

References