Skip to main content
VulnerabilityPublished Updated

CVE-2026-64515: Linux kernel · wifi: mac80211: fix MLE defragmentation

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 8.3 High · fixed in a74e893f30db64cdce0fc7a96d3baa417bcd55f5 : patch Linux kernel soon.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% 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
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in a74e893f30db64cdce0fc7a96d3baa417bcd55f5, 722b3f86df80644463d29fe5451e30a617f74500, 55c479aae99b120489a432db9c717484e523dfd6 +1
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jul 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 a74e893f30db64cdce0fc7a96d3baa417bcd55f5, 722b3f86df80644463d29fe5451e30a617f74500, 55c479aae99b120489a432db9c717484e523dfd6 or 1f573e17bcb7275ddd1c8f47f46ae0faf0e902a4.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 4d70e9c5488dd57ff5fcabe4d4ecf3d9dd4555ff, < a74e893f30db64cdce0fc7a96d3baa417bcd55f5
Fixed in
  • a74e893f30db64cdce0fc7a96d3baa417bcd55f5
LinuxLinuxAffected
  • ≥ 4d70e9c5488dd57ff5fcabe4d4ecf3d9dd4555ff, < 722b3f86df80644463d29fe5451e30a617f74500
Fixed in
  • 722b3f86df80644463d29fe5451e30a617f74500
LinuxLinuxAffected
  • ≥ 4d70e9c5488dd57ff5fcabe4d4ecf3d9dd4555ff, < 55c479aae99b120489a432db9c717484e523dfd6
Fixed in
  • 55c479aae99b120489a432db9c717484e523dfd6
LinuxLinuxAffected
  • ≥ 4d70e9c5488dd57ff5fcabe4d4ecf3d9dd4555ff, < 1f573e17bcb7275ddd1c8f47f46ae0faf0e902a4
Fixed in
  • 1f573e17bcb7275ddd1c8f47f46ae0faf0e902a4
LinuxLinuxAffected
  • =6.9
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: fix MLE defragmentation If either reconf or EPCS multi-link element (MLE) is contained in a non-transmitted profile, the defragmentation routine is called with a pointer to the defragmented copy, but the original elements. This is incorrect for two reasons: - if the original defragmentation was needed, it will not find the correct data - if the original frame is at a higher address, the parsing will potentially overrun the heap data (though given the layout of the buffers, only into the new defragmentation buffer, and then it has to stop and fail once that's filled with copied data. Fix it by tracking the container along with the pointer and in doing so also unify the two almost identical defragmentation routines.

References

Community reviews

Loading reviews…