Local kernel corruption via ALSA TLV bounds errors
Published Aug 15, 2026 · Updated Aug 15, 2026
Heap buffer overflow in affected Linux kernels allows local users to corrupt memory and read adjacent heap data through ALSA TLV kcontrols. The bytes_ext_put and bytes_ext_get checks compare payload lengths with the full ipc_control_data allocation even though cdata->data begins after the fixed header; the put restore path also writes through the wrong pointer. Exploitation requires local access to an ALSA sound control device exposing an affected SOF IPC3 bytes_ext control, and it can disclose kernel heap data, corrupt adjacent objects, or crash the system.
Summary
What happened
Heap buffer overflow in affected Linux kernels allows local users to corrupt memory and read adjacent heap data through ALSA TLV kcontrols. The bytes_ext_put and bytes_ext_get checks compare payload lengths with the full ipc_control_data allocation even though cdata->data begins after the fixed header; the put restore path also writes through the wrong pointer. Exploitation requires local access to an ALSA sound control device exposing an affected SOF IPC3 bytes_ext control, and it can disclose kernel heap data, corrupt adjacent objects, or crash the system.
The record
- CVE
- CVE-2026-72262
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 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.
- Affected versionversion=5.18
- Affected versionversion=67ec2a091630c28ea8d05db2bd7178a05b04b7e6 <121577383b5cf221e86581e0f2bcca4c66f17469
- Affected versionversion=67ec2a091630c28ea8d05db2bd7178a05b04b7e6 <1adde1941bba7b0d7104b86ed819d48d81cb0ad9
- Affected versionversion=67ec2a091630c28ea8d05db2bd7178a05b04b7e6 <eaa67e139c9217099e2a7b717aeeb46c65de3494
- Affected versionversion=67ec2a091630c28ea8d05db2bd7178a05b04b7e6 <f4933e1d11b97b6a0951648b7c3e53850e1b33a9
- Affected versionversion=67ec2a091630c28ea8d05db2bd7178a05b04b7e6 <fd46668d538993218eea19c6925c868ac0f2630c
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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