Kernel-memory disclosure via truncated L2CAP response
Published Apr 3, 2026 · Updated Apr 3, 2026
Out-of-bounds read in the Linux Kernel Bluetooth L2CAP handler allows physically proximate attackers to expose adjacent kernel memory. l2cap_information_rsp() accepts a four-byte success response, then get_unaligned_le32() or rsp->data[0] reads one to four bytes beyond the header without confirming that cmd_len includes the payload. Exploitation requires Bluetooth radio range but no local credentials or user action, and the same response can trigger a kernel fault, oops, or panic.
Summary
What happened
Out-of-bounds read in the Linux Kernel Bluetooth L2CAP handler allows physically proximate attackers to expose adjacent kernel memory. l2cap_information_rsp() accepts a four-byte success response, then get_unaligned_le32() or rsp->data[0] reads one to four bytes beyond the header without confirming that cmd_len includes the payload. Exploitation requires Bluetooth radio range but no local credentials or user action, and the same response can trigger a kernel fault, oops, or panic.
The record
- CVE
- CVE-2026-31393
- Published
- Apr 3, 2026
- Updated
- Apr 3, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-125, T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 3, 2026CVE publishedPublication date reported by the CVE source.
- Apr 3, 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=2.6.24
- Affected versionversion=4e8402a3f884427f9233ba436459c158d1f2e114 <3b646516cba2ebc4b51a72954903326e7c1e443f
- Affected versionversion=4e8402a3f884427f9233ba436459c158d1f2e114 <807bd1258453c4c83f6ae9dbc1e7b44860ff40d0
- Affected versionversion=4e8402a3f884427f9233ba436459c158d1f2e114 <9aeacde4da0f02d42fd968fd32f245828b230171
- Affected versionversion=4e8402a3f884427f9233ba436459c158d1f2e114 <db2872d054e467810078e2b9f440a5b326a601b2
- Affected versionversion=4e8402a3f884427f9233ba436459c158d1f2e114 <dd815e6e3918dc75a49aaabac36e4f024d675101
- Affected versionversion=4e8402a3f884427f9233ba436459c158d1f2e114 <e7ff754e339e3d5ce29aa9f95352d0186df8fbd9
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