Local availability loss via stale-byte copy length
Published Aug 15, 2026 · Updated Aug 15, 2026
Incorrect-length buffer access in Linux allows local users to corrupt SOF IPC4 control data through a crafted control update. The sof_ipc4_bytes_put() function takes the copy length from the existing buffer header instead of validating and using the incoming ucontrol sof_abi_hdr.size, so changed sizes truncate new data or copy stale bytes. A low-privileged local user must reach the ASoC SOF IPC4 control path; public sources identify availability loss but do not specify whether the interruption is a hang, crash, or restart.
Summary
What happened
Incorrect-length buffer access in Linux allows local users to corrupt SOF IPC4 control data through a crafted control update. The sof_ipc4_bytes_put() function takes the copy length from the existing buffer header instead of validating and using the incoming ucontrol sof_abi_hdr.size, so changed sizes truncate new data or copy stale bytes. A low-privileged local user must reach the ASoC SOF IPC4 control path; public sources identify availability loss but do not specify whether the interruption is a hang, crash, or restart.
The record
- CVE
- CVE-2026-72304
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-805, T1499.004
- 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=6.4
- Affected versionversion=a062c8899fede2ab5660a817e9b602d3fa280a99 <038406abde0d0883419ec89425ea941ec8bbef95
- Affected versionversion=a062c8899fede2ab5660a817e9b602d3fa280a99 <266f936db83aee6ca6473bbb06259bda52bf4fc3
- Affected versionversion=a062c8899fede2ab5660a817e9b602d3fa280a99 <3ad673e7139cf214afd24321a829aad6575f4163
- Affected versionversion=a062c8899fede2ab5660a817e9b602d3fa280a99 <4cf6a7ebbf8787393b158b2cc341723e5bebc4a8
- Affected versionversion=a062c8899fede2ab5660a817e9b602d3fa280a99 <fb4293173db2d474d8fbc0e5ecf4943e6df2b40e
What conditions does exploitation require?
What is affected?
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