System crash via unchecked Bluetooth advertisement length
Published Feb 2, 2021 · Updated Aug 4, 2024
A heap-based buffer overflow in Linux Kernel 4.19 and later allows physically proximate attackers to crash systems via Bluetooth 5 advertisements. hci_le_ext_adv_report_evt passes an unchecked, up-to-255-byte report to store_pending_adv_report, which copies it into a 31-byte last_adv_data buffer. Triggering requires a Bluetooth 5 adapter and active advertisement scanning; the demonstrated consequence is a kernel panic.
Summary
What happened
A heap-based buffer overflow in Linux Kernel 4.19 and later allows physically proximate attackers to crash systems via Bluetooth 5 advertisements. hci_le_ext_adv_report_evt passes an unchecked, up-to-255-byte report to store_pending_adv_report, which copies it into a 31-byte last_adv_data buffer. Triggering requires a Bluetooth 5 adapter and active advertisement scanning; the demonstrated consequence is a kernel panic.
The record
- CVE
- CVE-2020-24490
- Published
- Feb 2, 2021
- Updated
- Aug 4, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 2, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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=all Linux kernel versions that support BlueZ
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
- Google Security Research BadVibes proof of conceptfunctional · demonstrated
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