CVE-2020-24490, named BadVibes, is a heap buffer overflow in the Linux kernel's Bluetooth event parser: a nearby attacker broadcasting oversized extended advertising data can crash, or possibly run code in, the kernel of any device scanning with a Bluetooth 5 controller. NVD scores it 6.5; mainline commit a2ec905 fixed it in Linux 5.8.
Vulnerability summary
CVSS base score
6.5
Medium severity
EPSS score (FIRST)
2.2%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2020-24490 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Linux kernel Bluetooth subsystem (net/bluetooth/hci_event.c) | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | 4.19 and later per Google; fixed by mainline commit a2ec905, first released in 5.8 (Debian tracker); NVD files it under cpe:2.3:a:bluez:bluez:- with no version |
| OpenEmbedded-Core bluez5 recipe (Yocto) | cpe:2.3:a:bluez:bluez:-:*:*:*:*:*:*:* | CVE_STATUS cpe-incorrect: not reported against the userspace BlueZ package (recipe read 2026-11-16) |
What does this mean for affected devices?
CVE-2020-24490 is the BleedingTooth flaw that needs no target address. Google's advisory GHSA-ccx2-w2r4-x649 describes a heap-based buffer overflow "affecting Linux kernel 4.19 and higher" in net/bluetooth/hci_event.c: a remote attacker in short distance "can broadcast extended advertising data and cause denial of service or possibly arbitrary code execution with kernel privileges on victim machines if they are equipped with Bluetooth 5 chips and are in scanning mode". Malicious or compromised Bluetooth chips can trigger it as well. A device that scans continuously, such as a gateway reading BLE sensors, meets that condition by design.
NVD scores it 6.5 (medium) with vector CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, weakness NVD-CWE-noinfo, and the Intel-written description says it "affects all Linux kernel versions that support BlueZ" (NVD). NVD's only configuration is the application CPE cpe:2.3:a:bluez:bluez:-, with no version and no Linux kernel entry. Version-matching tools can therefore attach the CVE to every BlueZ userspace package while missing the kernel that holds the bug.
The embedded build systems have had to correct for this. OpenEmbedded-Core's bluez5 recipe, used by Yocto-based firmware, sets CVE_STATUS for CVE-2020-24490 to cpe-incorrect with the note "This issue has kernel fixes rather than bluez fixes", the same status it gives CVE-2020-12351 and CVE-2020-12352. In a firmware image, check the kernel release, its BSP patches and CONFIG_BT, not the BlueZ version.
The fix is mainline commit a2ec905, "Bluetooth: fix kernel oops in store_pending_adv_report", by Alain Michaud and dated 2020-07-27, whose message reports the oops for extended advertising data larger than 31 bytes and stops caching extended advertising reports, since only legacy reports need that cache. The Debian tracker marks it as first released in Linux 5.8 and fixed in buster 4.19.146-1. The BleedingTooth write-up records that this fix reached mainline on 2020-07-30, well before the disclosure on 2020-10-13, and the commit title does not name the CVE, so a vendor kernel may carry it without listing CVE-2020-24490.
The CVE is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13), and FIRST EPSS gives it 0.0224, the 83rd percentile, in the 2026-11-15 dataset (CISA KEV, FIRST EPSS).
On a scanning gateway, turning scanning off removes the product's function, so the kernel fix is the remedy: a stable release at or above the fix for the branch, or a BSP kernel carrying a2ec905. Our BlueZ and Linux Bluetooth vulnerabilities in embedded devices guide covers kernel and BlueZ version checks, and our memory corruption fix guide covers this class of parser overflow.
Evidence
- Heap-based buffer overflow in net/bluetooth/hci_event.c affecting Linux 4.19 and higher; Bluetooth 5 chips in scanning mode; DoS or possibly kernel code execution. — Google Security Research GHSA-ccx2-w2r4-x649
- NVD CVSS v3.1 6.5 (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), NVD-CWE-noinfo; only configuration cpe:2.3:a:bluez:bluez:-. — NVD
- OpenEmbedded-Core bluez5 recipe: CVE_STATUS cpe-incorrect, kernel fixes rather than bluez fixes. — OpenEmbedded-Core bluez5 recipe
- Fix commit a2ec905 (2020-07-27): fix kernel oops in store_pending_adv_report. — Linux kernel commit a2ec905
- Debian: fix first released in 5.8; buster fixed in 4.19.146-1. — Debian Security Tracker
- Not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). — CISA KEV
- EPSS 0.02241 (83rd percentile), dataset 2026-11-15, read 2026-11-16. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Which devices are exposed to CVE-2020-24490?
Devices running Linux 4.19 or later without the fix that scan for Bluetooth advertisements with a Bluetooth 5 controller, per Google's advisory. BLE sensor gateways scan continuously, so they meet the condition whenever the radio is on (per Google Security Research).
Why does a scanner report CVE-2020-24490 against BlueZ?
NVD files it only under the BlueZ application CPE with no version, although the bug and fix are in the Linux kernel. OpenEmbedded-Core marks it cpe-incorrect for its bluez5 recipe for that reason (per NVD and OpenEmbedded-Core).
Which kernel versions fix CVE-2020-24490?
Mainline Linux 5.8 contains commit a2ec905, and Debian ships the fix in buster's 4.19.146-1. A BSP kernel needs that commit or a stable release that includes it (per git.kernel.org and the Debian Security Tracker).
Is CVE-2020-24490 in the CISA KEV catalog?
No, not as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.0224, the 83rd percentile, in the 2026-11-15 dataset (per CISA KEV and FIRST EPSS).
Questions about this page?