CVE-2026-64515High· 8.3▾ Twilight

wifi: mac80211: fix MLE defragmentation

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 cal…

▾ Twilight zone — High severity, or a signal on a lesser flaw

Depth score46/ 100 · Moderate

impact 45.7 · likelihood 0 · exploitation 0

⚡ Agent-ready:Raw markdown ↗JSON ↗

Proof of concept

Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.

…

Published

Jul 25, 2026

Updated

Oct 19, 2026

CVSS

8.3

Vendor

Linux

Product

Linux

CWE

—

Depth score

46 · Moderate

EPSS

0.24% · p14

Platforms

—

Source

CVEORG

Vector

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H

CISA SSVC

decided 2026-10-16

Exploitation: none
Automatable: no
Technical impact: partial

Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.

EPSS history

Exploit-prediction probability, daily snapshots since Oct 16.

0.2% → 0.2%

Timeline

Disclosure to exploitation, from the record and what we observed since indexing it.

4 events · 93 days

Jul 25, 2026Published
Disclosed via CVEORG
Oct 16, 2026EPSS first tracked
0.2%
Oct 19, 2026Record revised
Last analysed / modified upstream
Oct 26, 2026EPSS peak
0.2% → 0.2%

Linux #cve.org

Affected

Linux >= 4d70e9c5488dd57ff5fcabe4d4ecf3d9dd4555ff < 1f573e17bcb7275ddd1c8f47f46ae0faf0e902a4
Linux >= 4d70e9c5488dd57ff5fcabe4d4ecf3d9dd4555ff < 55c479aae99b120489a432db9c717484e523dfd6
Linux >= 4d70e9c5488dd57ff5fcabe4d4ecf3d9dd4555ff < 722b3f86df80644463d29fe5451e30a617f74500
Linux >= 4d70e9c5488dd57ff5fcabe4d4ecf3d9dd4555ff < a74e893f30db64cdce0fc7a96d3baa417bcd55f5
Linux 6.9

Full technical detail▾

Overview

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.

Affected

Linux >= 4d70e9c5488dd57ff5fcabe4d4ecf3d9dd4555ff < 1f573e17bcb7275ddd1c8f47f46ae0faf0e902a4
Linux >= 4d70e9c5488dd57ff5fcabe4d4ecf3d9dd4555ff < 55c479aae99b120489a432db9c717484e523dfd6
Linux >= 4d70e9c5488dd57ff5fcabe4d4ecf3d9dd4555ff < 722b3f86df80644463d29fe5451e30a617f74500
Linux >= 4d70e9c5488dd57ff5fcabe4d4ecf3d9dd4555ff < a74e893f30db64cdce0fc7a96d3baa417bcd55f5
Linux 6.9

Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

References

Related vulnerabilities

Connected by shared product, vendor, weakness, or advisory.

#cve.org

wifi: mac80211: fix MLE defragmentation

▾ Twilight zone — High severity, or a signal on a lesser flaw

Depth score46/ 100 · Moderate

impact 45.7 · likelihood 0 · exploitation 0

Overview

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.

Affected

Linux >= 4d70e9c5488dd57ff5fcabe4d4ecf3d9dd4555ff < 1f573e17bcb7275ddd1c8f47f46ae0faf0e902a4

Linux >= 4d70e9c5488dd57ff5fcabe4d4ecf3d9dd4555ff < 55c479aae99b120489a432db9c717484e523dfd6

Linux >= 4d70e9c5488dd57ff5fcabe4d4ecf3d9dd4555ff < 722b3f86df80644463d29fe5451e30a617f74500

Linux >= 4d70e9c5488dd57ff5fcabe4d4ecf3d9dd4555ff < a74e893f30db64cdce0fc7a96d3baa417bcd55f5

Linux 6.9