Skip to main content
VulnerabilityPublished Updated

CVE-2026-68470: Linux kernel · wifi: mac80211: validate extension-frame layout before RX

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High · fixed in 625fc704b19cb48d7d269ad54ffffb4d3bf9c7ed : patch Linux kernel soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in 625fc704b19cb48d7d269ad54ffffb4d3bf9c7ed, 57d503ce32eccfa7650065ca4c560f7e29a2e676, 7aba69b611007e11b9b93118ff8fe88998c3107f +1
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Linux kernel to 625fc704b19cb48d7d269ad54ffffb4d3bf9c7ed, 57d503ce32eccfa7650065ca4c560f7e29a2e676, 7aba69b611007e11b9b93118ff8fe88998c3107f or 1c3d9c6bd5b795f3b952b40d574c8e424e14a39b.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 09a740ce352e1a1d16b9984115514ba9a4f4704b, < 625fc704b19cb48d7d269ad54ffffb4d3bf9c7ed
Fixed in
  • 625fc704b19cb48d7d269ad54ffffb4d3bf9c7ed
LinuxLinuxAffected
  • ≥ 09a740ce352e1a1d16b9984115514ba9a4f4704b, < 57d503ce32eccfa7650065ca4c560f7e29a2e676
Fixed in
  • 57d503ce32eccfa7650065ca4c560f7e29a2e676
LinuxLinuxAffected
  • ≥ 09a740ce352e1a1d16b9984115514ba9a4f4704b, < 7aba69b611007e11b9b93118ff8fe88998c3107f
Fixed in
  • 7aba69b611007e11b9b93118ff8fe88998c3107f
LinuxLinuxAffected
  • ≥ 09a740ce352e1a1d16b9984115514ba9a4f4704b, < 1c3d9c6bd5b795f3b952b40d574c8e424e14a39b
Fixed in
  • 1c3d9c6bd5b795f3b952b40d574c8e424e14a39b
LinuxLinuxAffected
  • =5.10
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: validate extension-frame layout before RX Extension frames only have the extension header at the regular 802.11 header offset. The generic RX path can still reach helpers and interface dispatch code that read regular header address fields before unsupported extension subtypes are dropped. mac80211 currently only handles S1G beacon extension frames. Drop other extension subtypes before they can reach regular-header RX processing. For S1G beacons, linearize the SKB with the management-frame path and require the fixed S1G beacon header, including optional fixed fields indicated by frame control, before generic RX dispatch. Route S1G beacons through the station/default-link RX path without regular-header station lookup. Avoid regular-header address reads in the mac80211 RX paths that process S1G extension beacons, including accept-frame, duplicate-detection, address-copy, and MLO address-translation paths. Also make ieee80211_get_bssid() length-safe before returning the S1G source-address pointer.

References

Community reviews

Loading reviews…