CVE-2024-53144

What it actually does

The flaw permitted BR/EDR Just Works pairing to complete without requesting user confirmation (confirm_hint), unlike the LE path which enforces policy checks, enabling potential authentication bypass during pairing.

Why it matters to the business

Linux-based systems with Bluetooth could allow unauthorized device pairings that bypass security policies, increasing risk of data exposure or rogue device access across servers, embedded devices, and workstations; urgency is moderate given low EPSS and lack of KEV listing but high prevalence of the kernel.

How an attack unfolds

An attacker in Bluetooth range initiates a Just Works pairing request against a vulnerable Linux hci_event handler; the missing confirmation step allows the pairing to succeed automatically without user or policy intervention, after which the attacker can leverage the bonded connection for further actions. Threat actor mentions in related Linux kernel campaigns highlight espionage and financially motivated groups targeting similar kernel flaws.

How to fix it

Update the Linux kernel to commit 1860e379875dfe7271c649058aeddffe5afd9d0d or later; rebuild and deploy affected packages with the fix applied.

How to confirm the fix worked

Verify the presence of commit 1860e379875dfe7271c649058aeddffe5afd9d0d in the kernel source tree or check running kernel version against fixed releases; test Bluetooth pairing behavior to confirm confirmation prompts are now enforced for Just Works.

Typical attack path

1. Position within Bluetooth range of target Linux system
2. Send BR/EDR pairing request using Just Works method
3. Exploit absence of user confirmation request in hci_event
4. Complete pairing without policy enforcement
5. Establish authenticated session for subsequent attacks

How to detect it

Review kernel and Bluetooth daemon logs for pairing events that lack expected confirmation steps; look for hci_event entries related to BR/EDR Just Works without user interaction artifacts.

What your security team should do

• Prioritize kernel updates to the fixed commit across all Linux distributions and embedded systems
• Review and enforce Bluetooth security policies in userspace tools such as bluetoothd
• Monitor for downstream package updates in distributions using the affected kernel
• Consider disabling unnecessary Bluetooth interfaces until patched