Security Advisory

CVE-2020-12351: BleedingTooth BadKarma in L2CAP

Last updated:
  • CVE-2020-12351

CVE-2020-12351, named BadKarma, is a heap-based type confusion in the Linux kernel's Bluetooth L2CAP code that lets an attacker in radio range who knows a device's Bluetooth address crash the kernel or possibly run code with kernel privileges, with no pairing. NVD scores it 8.8; mainline commit f194256 fixes it, and Dell lists its Hybrid Client as affected.

Vulnerability summary

CVSS base score

8.8

High severity

EPSS score (FIRST)

7.8%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2020-12351 · Source: NVD

Affected components

ComponentCPEVersion range
Linux kernel Bluetooth subsystem (net/bluetooth/l2cap_core.c)cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*4.8 and later per Google; NVD: 4.7.7 to before 4.9.240, 4.10 to before 4.14.202, 4.15 to before 4.19.152, 4.20 to before 5.4.72, 5.5 to before 5.8.16, 5.9 up to 5.9.1
Dell Hybrid Client—1.0 and 1.1; remediated by a Security Addon (Dell DSA-2021-003)

What does this mean for affected devices?

CVE-2020-12351 is the most severe of the three BleedingTooth flaws that Google's Andy Nguyen disclosed on 2020-10-13. Google's advisory GHSA-h637-c88j-47wq places it in net/bluetooth/l2cap_core.c, affecting "Linux kernel 4.8 and higher", and states that "a remote attacker in short distance knowing the victim's bd address can send a malicious l2cap packet and cause denial of service or possibly arbitrary code execution with kernel privileges", adding that malicious Bluetooth chips can trigger it too. The BleedingTooth write-up chains it with the BadChoice leak, CVE-2020-12352, into zero-click code execution.

NVD scores it 8.8 (high) with vector CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, weakness CWE-20, and lists Linux kernel ranges whose upper bounds are the stable fixes 4.9.240, 4.14.202, 4.19.152, 5.4.72 and 5.8.16, plus 5.9 through 5.9.1 (NVD). NVD's references include a public BleedingTooth exploit for Linux 5.4 on Packet Storm. The CVE record itself, written by Intel, says "BlueZ", but the code and the fix are in the kernel: commit f194256, "Bluetooth: L2CAP: Fix calling sk_filter on non-socket based channel", dated 2020-08-06, gives channels such as A2MP their own filter callback.

The device angle comes from a vendor and from a build system. Dell's DSA-2021-003 names CVE-2020-12351 and CVE-2020-12352 for Dell Hybrid Client 1.0 and 1.1 and delivers the fix as a Security Addon. OpenEmbedded-Core, the base of Yocto builds, marks this CVE in its bluez5 recipe as cpe-incorrect with the note "This issue has kernel fixes rather than bluez fixes", so its CVE check does not report it against the userspace BlueZ package. In a firmware image the question is therefore the kernel version, its BSP patches, and whether CONFIG_BT is built at all.

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.0776, the 95th percentile, in the 2026-11-15 dataset (CISA KEV, FIRST EPSS). The Debian tracker lists the fix in stretch 4.9.240-1 (DLA-2420-1) and buster 4.19.152-1 (DSA-4774-1).

Device makers should move to a stable kernel at or above the fixed release for their branch, or ask the SoC vendor for a BSP kernel carrying f194256, and turn off CONFIG_BT_HS on kernels that still have it, which removes the A2MP channel used in the published chain. Our BlueZ and Linux Bluetooth vulnerabilities in embedded devices guide covers finding the kernel version and Bluetooth configuration in an image, and our Linux kernel CVEs in embedded devices guide covers triage by kernel branch and configuration.

How to fix this class of issueNo dedicated SoftWSP guide covers this weakness class; the fix is usually the vendor patch or firmware update referenced above. Our related guide explains how to plan and verify it: NIST SP 800-40 Rev. 4: enterprise patch management planning, explained.

Evidence

  • Heap-based type confusion in net/bluetooth/l2cap_core.c affecting Linux 4.8 and higher; remote attacker in short distance knowing the bd address; DoS or possibly kernel code execution; malicious chips can trigger it. — Google Security Research GHSA-h637-c88j-47wq
  • NVD CVSS v3.1 8.8 (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), CWE-20; ranges ending 4.9.240, 4.14.202, 4.19.152, 5.4.72, 5.8.16, plus 5.9 to 5.9.1; Packet Storm exploit reference. — NVD
  • Fix commit f194256 (2020-08-06): L2CAP: Fix calling sk_filter on non-socket based channel. — Linux kernel commit f194256
  • Dell Hybrid Client 1.0 and 1.1 affected by CVE-2020-12351 and CVE-2020-12352; Security Addon remediation. — Dell DSA-2021-003
  • OpenEmbedded-Core bluez5 recipe: CVE_STATUS cpe-incorrect, 'This issue has kernel fixes rather than bluez fixes'. — OpenEmbedded-Core bluez5 recipe
  • Debian fixed stretch in 4.9.240-1 (DLA-2420-1) and buster in 4.19.152-1 (DSA-4774-1). — Debian Security Tracker
  • Not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). — CISA KEV
  • EPSS 0.07756 (95th percentile), dataset 2026-11-15, read 2026-11-16. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. Google Security Research GHSA-h637-c88j-47wq (BadKarma)
  3. Google Security Research: BleedingTooth write-up
  4. Linux commit f194256: L2CAP: Fix calling sk_filter on non-socket based channel
  5. Dell DSA-2021-003: Dell Hybrid Client, Intel BlueZ vulnerabilities
  6. OpenEmbedded-Core: bluez5 recipe
  7. Debian Security Tracker
  8. CISA KEV
  9. FIRST EPSS

Frequently asked questions

Is CVE-2020-12351 a BlueZ bug or a Linux kernel bug?

A kernel bug. Google's advisory places it in net/bluetooth/l2cap_core.c and the fix is Linux commit f194256; the CVE text says BlueZ because Intel uses that name for the whole Linux Bluetooth stack. OpenEmbedded-Core marks it cpe-incorrect for its BlueZ package (per Google, git.kernel.org and OpenEmbedded-Core).

Which kernel versions fix CVE-2020-12351?

NVD's ranges end at the stable releases 4.9.240, 4.14.202, 4.19.152, 5.4.72 and 5.8.16; Debian ships the fix in 4.9.240-1 and 4.19.152-1. A vendor BSP kernel is fixed only if it carries commit f194256 (per NVD and the Debian Security Tracker).

Which devices does a vendor list as affected by CVE-2020-12351?

Dell's DSA-2021-003 lists Dell Hybrid Client 1.0 and 1.1 and provides a Security Addon. Any embedded Linux product with a Bluetooth-enabled kernel in the affected ranges is exposed until patched (per Dell and NVD).

Is CVE-2020-12351 in the CISA KEV catalog?

No, not as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.0776, the 95th percentile, in the 2026-11-15 dataset, and NVD references a public exploit (per CISA KEV, FIRST EPSS and NVD).