Kernel stack corruption via oversized USB control request
Published May 1, 2026 · Updated May 1, 2026
Out-of-bounds write in the Linux Kernel allows physically proximate attackers to corrupt kernel stack memory through USB control requests. In f_audio_complete(), memcpy uses the host-influenced req->length to write into a four-byte data variable without validating the received payload size. The condition requires a legacy UAC1 USB gadget attached to a hostile USB host, and the overwrite corrupts adjacent kernel stack state.
Summary
What happened
Out-of-bounds write in the Linux Kernel allows physically proximate attackers to corrupt kernel stack memory through USB control requests. In f_audio_complete(), memcpy uses the host-influenced req->length to write into a four-byte data variable without validating the received payload size. The condition requires a legacy UAC1 USB gadget attached to a hostile USB host, and the overwrite corrupts adjacent kernel stack state.
The record
- CVE
- CVE-2026-31720
- Published
- May 1, 2026
- Updated
- May 1, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-787, T1200
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 1, 2026CVE publishedPublication date reported by the CVE source.
- May 1, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0d41772d98dcaf6c17e875b7d0ea0154ae1191ee
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <21b11e8581285c6f10ef43d05df349d445f24273
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <26304d124e7f0383f8fe1168b5801a0ac7e16b1c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <557d1d4e862eccd0b74cc377b66de3e1e8d49605
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6e0e34d85cd46ceb37d16054e97a373a32770f6c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8e5eb1d6e6a3d7bbea9c92132d0cda5793176426
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <be2d32f0c3fe333d14c0a9ca90328dacbc3e06b8
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c6da4fed7537aec19880c24f6c3a95065adb1406
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.
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