Kernel stack disclosure via unchecked build-info length
Published May 30, 2024 · Updated Aug 5, 2026
Information disclosure in the Linux QCA Bluetooth driver allows attackers to read kernel stack data from debugfs after malformed firmware replies. qca_read_fw_build_info() trusted the controller-supplied build-label length without confirming that the reply contained that many bytes, then exposed residual stack contents through the firmware-information field. Reachability requires the QCA Bluetooth path, a malformed build-info reply, and access to the exported debugfs field; the bounded consequence is kernel-memory disclosure.
Summary
What happened
Information disclosure in the Linux QCA Bluetooth driver allows attackers to read kernel stack data from debugfs after malformed firmware replies. qca_read_fw_build_info() trusted the controller-supplied build-label length without confirming that the reply contained that many bytes, then exposed residual stack contents through the firmware-information field. Reachability requires the QCA Bluetooth path, a malformed build-info reply, and access to the exported debugfs field; the bounded consequence is kernel-memory disclosure.
The record
- CVE
- CVE-2024-36032
- Published
- May 30, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-668, T1005
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- May 30, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.12
- Affected versionversion=c0187b0bd3e94c48050687d87b2c3c9fbae98ae9 <57062aa13e87b1a78a4a8f6cb5fab6ba24f5f488
- Affected versionversion=c0187b0bd3e94c48050687d87b2c3c9fbae98ae9 <62d5550ab62042dcceaf18844d0feadbb962cffe
- Affected versionversion=c0187b0bd3e94c48050687d87b2c3c9fbae98ae9 <6b63e0ef4d3ce0080395e5091fba2023f246c45a
- Affected versionversion=c0187b0bd3e94c48050687d87b2c3c9fbae98ae9 <a571044cc0a0c944e7c12237b6768aeedd7480e1
- Affected versionversion=c0187b0bd3e94c48050687d87b2c3c9fbae98ae9 <cda0d6a198e2a7ec6f176c36173a57bdd8af7af2
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