Bluetooth traffic compromise via zero-padded RNG output
Published Mar 5, 2024 · Updated Aug 5, 2026
Insufficient randomness in Linux allows adjacent attackers to decrypt or forge Bluetooth traffic through predictable cryptographic keys. qcom_rng_read stops when PRNG_STATUS_DATA_AVAIL clears, and qcom_rng_generate ignores the partial-read result while zero-padding the remaining output. Exploitation requires a Qualcomm device using qcom-rng as its default generator for Bluetooth pairing secrets; the documented impact is disclosure and forgery, not service interruption.
Summary
What happened
Insufficient randomness in Linux allows adjacent attackers to decrypt or forge Bluetooth traffic through predictable cryptographic keys. qcom_rng_read stops when PRNG_STATUS_DATA_AVAIL clears, and qcom_rng_generate ignores the partial-read result while zero-padding the remaining output. Exploitation requires a Qualcomm device using qcom-rng as its default generator for Bluetooth pairing secrets; the documented impact is disclosure and forgery, not service interruption.
The record
- CVE
- CVE-2022-48629
- Published
- Mar 5, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1557
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 5, 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.19
- Affected versionversion=ceec5f5b59882b871a722ca4d49b767a09a4bde9 <0f9b7b8df17525e464294c916acc8194ce38446b
- Affected versionversion=ceec5f5b59882b871a722ca4d49b767a09a4bde9 <184f7bd08ce56f003530fc19f160d54e75bf5c9d
- Affected versionversion=ceec5f5b59882b871a722ca4d49b767a09a4bde9 <485995cbc98a4f77cfd4f8ed4dd7ff8ab262964d
- Affected versionversion=ceec5f5b59882b871a722ca4d49b767a09a4bde9 <a680b1832ced3b5fa7c93484248fd221ea0d614b
- Affected versionversion=ceec5f5b59882b871a722ca4d49b767a09a4bde9 <a8e32bbb96c25b7ab29b1894dcd45e0b3b08fd9d
- Affected versionversion=ceec5f5b59882b871a722ca4d49b767a09a4bde9 <ab9337c7cb6f875b6286440b1adfbeeef2b2b2bd
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