CVE-2026-64515

Heap overrun via mismatched MLE container parsing

Published Jul 25, 2026 · Updated Jul 25, 2026

Heap overrun in the mac80211 subsystem of Linux Kernel allows attackers to overrun kernel heap data via crafted Wi-Fi MLEs. The MLE defragmentation path passes a defragmented-copy pointer together with elements from the original container, so parsing can run beyond the copied heap buffer. Exploitation requires reception of a reconf or EPCS MLE in a non-transmitted profile over an adjacent Wi-Fi link; parsing stops after filling the adjacent defragmentation buffer.

CVSS severity8.3
High
EPSS probability0.24%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Heap overrun in the mac80211 subsystem of Linux Kernel allows attackers to overrun kernel heap data via crafted Wi-Fi MLEs. The MLE defragmentation path passes a defragmented-copy pointer together with elements from the original container, so parsing can run beyond the copied heap buffer. Exploitation requires reception of a reconf or EPCS MLE in a non-transmitted profile over an adjacent Wi-Fi link; parsing stops after filling the adjacent defragmentation buffer.

The record

CVE
CVE-2026-64515
Published
Jul 25, 2026
Updated
Jul 25, 2026
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
CWE-823
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jul 25, 2026CVE publishedPublication date reported by the CVE source.
  2. Jul 25, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=4d70e9c5488dd57ff5fcabe4d4ecf3d9dd4555ff <1f573e17bcb7275ddd1c8f47f46ae0faf0e902a4
  2. Affected versionversion=4d70e9c5488dd57ff5fcabe4d4ecf3d9dd4555ff <55c479aae99b120489a432db9c717484e523dfd6
  3. Affected versionversion=4d70e9c5488dd57ff5fcabe4d4ecf3d9dd4555ff <722b3f86df80644463d29fe5451e30a617f74500
  4. Affected versionversion=4d70e9c5488dd57ff5fcabe4d4ecf3d9dd4555ff <a74e893f30db64cdce0fc7a96d3baa417bcd55f5
  5. Affected versionversion=6.9

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

The Linux Kernel Organization · Linux Kernelversion=4d70e9c5488dd57ff5fcabe4d4ecf3d9dd4555ff <1f573e17bcb7275ddd1c8f47f46ae0faf0e902a4; version=4d70e9c5488dd57ff5fcabe4d4ecf3d9dd4555ff <55c479aae99b120489a432db9c717484e523dfd6; version=4d70e9c5488dd57ff5fcabe4d4ecf3d9dd4555ff <722b3f86df80644463d29fe5451e30a617f74500; version=4d70e9c5488dd57ff5fcabe4d4ecf3d9dd4555ff <a74e893f30db64cdce0fc7a96d3baa417bcd55f5; version=6.9

Published CVSS scores

8.3Linux Kernel CVE teamCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H
7.0Red HatCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-823Use of Out-of-range Pointer Offset

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo