Security Advisory

CVE-2024-8805: BlueZ HID over GATT Access Control Flaw

Last updated:
  • CVE-2024-8805

CVE-2024-8805 is ZDI-24-1229, an access control flaw reported against BlueZ: a nearby, unauthenticated Bluetooth device could pair without the authorization step the host should require. NVD scores it 8.8. The fix is in the Linux kernel, not the bluez package: kernels from 6.12-rc2, and stable releases such as 6.1.113 and 6.6.55, carry it.

Vulnerability summary

CVSS base score

8.8

High severity

EPSS score (FIRST)

2.0%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2024-8805 · Source: NVD

Affected components

ComponentCPEVersion range
BlueZ / Linux Bluetooth stack (kernel net/bluetooth/hci_event.c, Just Works pairing)cpe:2.3:a:bluez:bluez:5.77:*:*:*:*:*:*:*NVD and the ZDI CNA list BlueZ 5.77; the fix is kernel commit b25e11f978b6 (6.12-rc2); stable kernels 5.10.236, 5.15.180, 6.1.113, 6.6.55, 6.10.14, 6.11.3 per the CVE-2024-53144 record
Debian linux and linux-6.1 packages—fixed in 6.1.115-1 (bookworm), 6.11.4-1 (unstable), linux-6.1 6.1.119-1~deb11u1 for bullseye (DLA-4008-1); no bluez package fix listed

What does this mean for affected devices?

NVD's description, from ZDI: "BlueZ HID over GATT Profile Improper Access Control Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of BlueZ. Authentication is not required to exploit this vulnerability. The specific flaw exists within the implementation of the HID over GATT Profile. The issue results from the lack of authorization prior to allowing access to functionality." NVD's Primary score is CVSS v3.1 8.8 (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), the same as ZDI's own CVSS v3.0 score; NVD assigns no CWE, and ZDI classes it CWE-284, improper access control. NVD's only CPE is BlueZ 5.77. The record was published on 2024-11-22 (NVD, CVE record).

What does the fix change?

ZDI-24-1229 credits Michael Randrianantenaina, lists the report to the vendor on 2024-09-10 and the advisory on 2024-09-17, and links a Bluetooth patch by Luiz Augusto von Dentz as the fix. That patch, "Bluetooth: hci_event: Align BR/EDR JUST_WORKS paring with LE", changes the kernel, not the bluez user-space package. Before it, when the host was the acceptor and neither side required MITM protection, the kernel auto-accepted Just Works pairing. After it, the kernel always asks user space to confirm, as it already did for LE, so bluetoothd's policy (for example JustWorksRepairing in main.conf) decides. ZDI's title names HID over GATT, while the patch changes BR/EDR pairing in hci_event.c; the patch itself carries the tag CVE: CVE-2024-8805.

Is this the same as CVE-2024-53144?

Yes. The Linux kernel CNA later assigned CVE-2024-53144 to the same commit, and the Debian tracker notes that CVE-2024-8805 is "likely to be rejected as Linux kernel CNA assigned later CVE-2024-53144". As of 2026-11-18 NVD still lists CVE-2024-8805 with status Modified, and the CVE record is published, so scanners can report either ID or both. Treat a hit on either one as a single kernel fix to verify.

Which devices are affected and how do you fix it?

Any Linux-based gateway, hub, head unit or appliance with Bluetooth Classic (BR/EDR) enabled runs this kernel code, whatever BlueZ version its user space ships. Debian fixed it in linux 6.1.115-1 for bookworm and 6.11.4-1 for unstable, and in linux-6.1 6.1.119-1~deb11u1 for bullseye through DLA-4008-1; it lists no bluez package fix. For your own image, check the kernel version against the stable releases in the CVE-2024-53144 record (5.10.236, 5.15.180, 6.1.113, 6.6.55, 6.10.14, 6.11.3, or 6.12 and later) or confirm the commit is backported. Updating only BlueZ leaves the device exposed.

Our Bluetooth LE security guide puts this in the context of other stack bugs, the BlueZ guide covers the Linux stack, and CVE-2023-45866 is the earlier BlueZ flaw where a fake keyboard paired without confirmation. CVE-2024-34722 is a 2024 pairing bypass in Android's stack.

CVE-2024-8805 is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.0204, the 81.4th percentile, in the 2026-11-17 dataset (CISA KEV, FIRST EPSS).

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

  • NVD: BlueZ HID over GATT Profile Improper Access Control RCE; network-adjacent, no authentication; lack of authorization prior to allowing access to functionality; ZDI-CAN-25177. NVD Primary CVSS v3.1 8.8 AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H; ZDI CVSS v3.0 8.8; NVD-CWE-noinfo; ZDI CWE-284; CPE bluez 5.77; status Modified; published 2024-11-22. — NVD
  • ZDI-24-1229 (September 17th, 2024): CVSS 8.8; affected vendor/product BlueZ; additional details link patchwork patch 20240912204458.3037144-1-luiz.dentz and bluetooth-next commit 370e38c32529; timeline reported 2024-09-10, release 2024-09-17, updated 2024-10-09; credit Michael Randrianantenaina. — Zero Day Initiative
  • Kernel commit b25e11f978b6 'Bluetooth: hci_event: Align BR/EDR JUST_WORKS paring with LE' (Luiz Augusto von Dentz, 2024-09-12): always request user confirmation with confirm_hint set, bluetoothd policy (main.conf:JustWorksRepairing); tag 'CVE: CVE-2024-8805'; Fixes ba15a58b179e; removes the auto-accept when neither side had MITM. — kernel.org
  • Debian tracker CVE-2024-8805: fix https://git.kernel.org/linus/b25e11f978b6 (6.12-rc2); linux bookworm 6.1.115-1, unstable 6.11.4-1, linux-6.1 bullseye 6.1.119-1~deb11u1 (DLA-4008-1); note 'CVE-2024-8805 likely to be rejected as Linux kernel CNA assigned later CVE-2024-53144'. — Debian security tracker
  • DLA-4008-1 (January 02, 2025): linux-6.1 6.1.119-1~deb11u1 fixes CVE-2024-8805 among others. — Debian LTS
  • CVE record CVE-2024-8805: state PUBLISHED, assigner zdi, affected BlueZ 5.77. — CVE.org
  • CVE-2024-53144 record (Linux CNA): unaffected 5.10.236, 5.15.180, 6.1.113, 6.6.55, 6.10.14, 6.11.3, 6.12. — CVE.org
  • CVE-2024-8805 is not in the CISA KEV catalog, version 2026.11.17 (1,782 entries), checked 2026-11-18. — CISA KEV
  • EPSS 0.02036, percentile 0.8144, dataset 2026-11-17. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. CVE record: CVE-2024-8805
  3. Zero Day Initiative ZDI-24-1229
  4. Linux kernel: Bluetooth: hci_event: Align BR/EDR JUST_WORKS paring with LE
  5. Debian security tracker: CVE-2024-8805
  6. Debian LTS DLA-4008-1 (linux-6.1)
  7. CVE record: CVE-2024-53144
  8. CISA KEV
  9. FIRST EPSS

Frequently asked questions

Does updating the bluez package fix CVE-2024-8805?

No. The fix ZDI links is a Linux kernel commit in net/bluetooth/hci_event.c, released in 6.12-rc2 and stable kernels, and Debian lists fixed linux packages but no bluez fix (per ZDI-24-1229, the kernel commit and the Debian security tracker).

Are CVE-2024-8805 and CVE-2024-53144 the same vulnerability?

They describe the same kernel fix. The commit is tagged CVE-2024-8805, the kernel CNA assigned CVE-2024-53144 to it later, and Debian expects CVE-2024-8805 to be rejected; as of 2026-11-18 both records are still published (per the kernel commit, Debian and NVD).

Which kernel versions contain the fix?

6.12 and later, and the stable releases 5.10.236, 5.15.180, 6.1.113, 6.6.55, 6.10.14 and 6.11.3, according to the CVE-2024-53144 record. Debian fixed it in 6.1.115-1 for bookworm (per the CVE record and the Debian security tracker).

Is CVE-2024-8805 exploited in the wild?

It is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.0204, the 81.4th percentile, in the 2026-11-17 dataset (per CISA KEV and FIRST EPSS).