Kernel memory corruption via unchecked firmware lengths
Published May 30, 2024 · Updated Aug 5, 2026
Memory corruption in the QCA Bluetooth firmware parser in Linux allows local users to corrupt kernel memory via a crafted firmware file. The qca_tlv_check_data function trusts a 24-bit TLV length and advances through NVM tags beyond the vmalloced firmware buffer, then reads and writes out of bounds. Exploitation requires write access to a local firmware search path and QCA Bluetooth device initialization; the corruption can disclose data, alter kernel memory, or panic the system.
Summary
What happened
Memory corruption in the QCA Bluetooth firmware parser in Linux allows local users to corrupt kernel memory via a crafted firmware file. The qca_tlv_check_data function trusts a 24-bit TLV length and advances through NVM tags beyond the vmalloced firmware buffer, then reads and writes out of bounds. Exploitation requires write access to a local firmware search path and QCA Bluetooth device initialization; the corruption can disclose data, alter kernel memory, or panic the system.
The record
- CVE
- CVE-2024-36880
- Published
- May 30, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
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=4.3
- Affected versionversion=83e81961ff7ef75f97756f316caea5aa6bcc19cc <02f05ed44b71152d5e11d29be28aed91c0489b4e
- Affected versionversion=83e81961ff7ef75f97756f316caea5aa6bcc19cc <1caceadfb50432dbf6d808796cb6c34ebb6d662c
- Affected versionversion=83e81961ff7ef75f97756f316caea5aa6bcc19cc <2e4edfa1e2bd821a317e7d006517dcf2f3fac68d
- Affected versionversion=83e81961ff7ef75f97756f316caea5aa6bcc19cc <427281f9498ed614f9aabc80e46ec077c487da6d
- Affected versionversion=83e81961ff7ef75f97756f316caea5aa6bcc19cc <ed53949cc92e28aaa3463d246942bda1fbb7f307
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