CVE-2024-53144 is a Linux kernel Bluetooth flaw: as the acceptor of BR/EDR pairing with no MITM requirement, the kernel accepted Just Works pairing on its own instead of asking bluetoothd, so a nearby device could bond silently. NVD scores it 5.5, the kernel CNA 8.8. Kernels 6.12, 6.6.55, 6.1.113 and 5.15.180 fix it.
Vulnerability summary
CVSS base score
5.5
Medium severity
EPSS score (FIRST)
0.4%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2024-53144 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Linux kernel Bluetooth (net/bluetooth/hci_event.c) | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | 3.16 up to 5.10.236, 5.11 to 5.15.180, 5.16 to 6.1.113, 6.2 to 6.6.55, 6.7 to 6.10.14, 6.11 to 6.11.3 (exclusive), plus backports in 3.2.61+, 3.4.98+, 3.10.48+, 3.12.25+, 3.14.12+, 3.15.5+ (NVD, kernel CNA); fixed in 6.12 |
| Debian linux and linux-6.1 packages | — | fixed in 5.10.237-1 for bullseye (DLA-4178-1), 6.1.115-1 (bookworm), 6.11.4-1 (unstable), linux-6.1 6.1.119-1~deb11u1 (DLA-4008-1) |
What does this mean for affected devices?
The kernel CNA's description: "Bluetooth: hci_event: Align BR/EDR JUST_WORKS paring with LE. This aligned BR/EDR JUST_WORKS method with LE which since 92516cd97fd4 ("Bluetooth: Always request for user confirmation for Just Works") always request user confirmation with confirm_hint set since the likes of bluetoothd have dedicated policy around JUST_WORKS method (e.g. main.conf:JustWorksRepairing). CVE: CVE-2024-8805". NVD's Primary score is CVSS v3.1 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), a local denial-of-service rating, with no CWE. The kernel CNA scores it 8.8 (AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and explains that "the kernel never invokes mgmt_user_confirm_request, so bluetoothd and the user are never consulted and the bond completes silently". The record was published on 2024-12-17 (NVD, CVE record).
What was wrong?
In hci_user_confirm_request_evt, when the pairing needed no MITM protection and the host was not the initiator, the kernel asked user space only if one side had set the MITM flag; with neither set, it accepted the pairing itself. The fix, by Luiz Augusto von Dentz, removes that exception: the kernel now always passes the request to user space with confirm_hint set, as it has done for LE, so bluetoothd's policy applies. The commit names ba15a58b179e ("Bluetooth: Fix SSP acceptor just-works confirmation without MITM") as the change it fixes. The kernel CNA's rationale says an attacker that offers NoInputNoOutput and bonding without MITM makes the silent accept deterministic, and that a bond can then open profiles such as HID; CISA's SSVC entry records exploitation "none", not automatable, technical impact "total".
Which kernels are affected?
The affected range starts at 3.16 and at the stable backports of ba15a58b179e (3.2.61, 3.4.98, 3.10.48, 3.12.25, 3.14.12 and 3.15.5). Fixed versions: 5.10.236, 5.15.180, 6.1.113, 6.6.55, 6.10.14, 6.11.3 and 6.12. Debian fixed it in linux 5.10.237-1 for bullseye (DLA-4178-1), 6.1.115-1 for bookworm and 6.11.4-1 for unstable, and in linux-6.1 6.1.119-1~deb11u1 (DLA-4008-1), per the Debian tracker.
What should device makers do?
Every embedded Linux product with Bluetooth Classic enabled runs this code: gateways, hubs, infotainment units and handhelds. Check the kernel version in the image against the list above, or confirm the backport in a vendor kernel. The same commit is tracked by ZDI as CVE-2024-8805, filed against BlueZ, so a scanner may report both IDs for one fix; updating the bluez package alone does not close it. Our Linux kernel CVE guide explains how to triage kernel CNA records, the BlueZ guide covers the Bluetooth stack, and CVE-2020-12351 and CVE-2023-45866 are earlier Linux Bluetooth flaws.
CVE-2024-53144 is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.00419, the 37th percentile, in the 2026-11-17 dataset (CISA KEV, FIRST EPSS).
Evidence
- NVD: description as kernel commit; NVD Primary CVSS v3.1 5.5 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H; kernel CNA (416baaa9...) 8.8 AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H; NVD-CWE-noinfo; CPE ranges 3.2.61-<3.3, 3.4.98-<3.5, 3.10.48-<3.11, 3.12.25-<3.13, 3.14.12-<3.15, 3.15.5-<3.16, 3.16.1-<5.10.236, 5.11-<5.15.180, 5.16-<6.1.113, 6.2-<6.6.55, 6.7-<6.10.14, 6.11-<6.11.3, 3.16 and rc, 6.12-rc1; references ZDI-24-1229, DLA-4008-1, DLA-4178-1; published 2024-12-17. — NVD
- CVE record (Linux CNA, updated 2026-10-15): affected from 3.16, unaffected 5.10.236, 5.15.180, 6.1.113, 6.6.55, 6.10.14, 6.11.3, 6.12; CVSS 8.8 with scenario text 'the kernel never invokes mgmt_user_confirm_request, so bluetoothd and the user are never consulted and the bond completes silently'; attacker controls IO capability NoInputNoOutput and bonding without MITM; CISA-ADP SSVC exploitation none, automatable no, technical impact total. — CVE.org
- Kernel commit b25e11f978b6 (Luiz Augusto von Dentz, 2024-09-12): 'If no side requires MITM protection; use JUST_CFM method'; removes '(loc_mitm || rem_mitm)' condition; Fixes: ba15a58b179e ('Bluetooth: Fix SSP acceptor just-works confirmation without MITM'); CVE: CVE-2024-8805; Cc stable. — kernel.org
- Debian tracker CVE-2024-53144: linux bullseye 5.10.237-1 (DLA-4178-1), bookworm 6.1.115-1, unstable 6.11.4-1, linux-6.1 bullseye 6.1.119-1~deb11u1 (DLA-4008-1); fix b25e11f (6.12-rc2). — Debian security tracker
- DLA-4178-1 (May 25, 2025): linux 5.10.237-1. — Debian LTS
- DLA-4008-1 (January 02, 2025): linux-6.1 6.1.119-1~deb11u1. — Debian LTS
- CVE-2024-53144 is not in the CISA KEV catalog, version 2026.11.17 (1,782 entries), checked 2026-11-18. — CISA KEV
- EPSS 0.00419, percentile 0.36772, dataset 2026-11-17. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Why does NVD score CVE-2024-53144 5.5 when the kernel CNA says 8.8?
NVD's Primary score treats it as a local denial of service (AV:L, availability only). The kernel CNA scores it as an adjacent attack from radio range that silently creates a bond, with high confidentiality, integrity and availability impact (per NVD and the CVE record).
Which Linux kernel versions fix CVE-2024-53144?
6.12 and the stable releases 5.10.236, 5.15.180, 6.1.113, 6.6.55, 6.10.14 and 6.11.3. Debian fixed it in 5.10.237-1 (bullseye) and 6.1.115-1 (bookworm) (per the CVE record and the Debian security tracker).
Is CVE-2024-53144 the same as CVE-2024-8805?
Yes, both point at the same kernel commit, which carries the tag CVE-2024-8805; the kernel CNA assigned CVE-2024-53144 to it later. Fixing the kernel resolves both (per the kernel commit and the Debian security tracker).
Is CVE-2024-53144 in the CISA KEV catalog?
No, not as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.00419, the 37th percentile, in the 2026-11-17 dataset (per CISA KEV and FIRST EPSS).
Questions about this page?