CVE-2026-74510

Bluetooth: mgmt: fix UAF in pair command cancellation

HIGH
7.8
CVSS Score
Published: August 15, 2026 at 12:27 PM UTC
Updated: October 16, 2026 at 08:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: mgmt: fix UAF in pair command cancellation The pairing completion and authentication failure callbacks look up the pending MGMT_OP_PAIR_DEVICE command by walking hdev->mgmt_pending. The lookup returned a command that was still linked on the shared pending list, without keeping mgmt_pending_lock held for the later dereference and removal. A concurrent MGMT_OP_CANCEL_PAIR_DEVICE request can remove and free the same pending command before the callback uses it. The reverse race is also possible when cancel_pair_device() gets a command from pending_find() and a callback removes it before the cancel path dereferences it. This can lead to a use-after-free and a second list_del(). Make the pairing lookup helpers transfer ownership of the pending command by removing it from hdev->mgmt_pending while holding mgmt_pending_lock. The callbacks and cancel path then complete the command and free it directly, so racing paths cannot find or free the same command again. Take a temporary hci_conn reference in cancel_pair_device() because the command completion drops the reference stored in the pending command.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.39e9a416b5ce0c0f93819f55d34cf6882196e9c3b2
Vendor states this is fixed in 50af4280a587c9971b5388cbc438f1324e626b7b (fixed)
Vendor states this is fixed in 51be7280980fddc90ebe874a69c2fe8ab02bb46a (fixed)
Vendor states this is fixed in 7c2a152a897cd1c184b2051484d4f74d803e7f4a (fixed)
Vendor states this is fixed in 86ed4dd6548ccf277bc691bc912ca06e76b9d80c (fixed)
Vendor states this is fixed in c569def320aa8b1fde89227e2ea96606790fd86d (fixed)
Vendor states this is fixed in d0a7b48ad0921bd88effaee10bf970ab1d5d0ddd (fixed)
Vendor states this is fixed in 2.6.39 (unaffected)
Vendor states this is fixed in 6.1.184 (unaffected)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.6.151 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card