Bluetooth: Serialize SMP remote OOB data access
Summary
| CVE | CVE-2026-98738 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-18 16:17:27 UTC |
| Updated | 2026-10-21 13:21:41 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: Serialize SMP remote OOB data access
build_pairing_cmd() looks up remote OOB data and copies its contents
without holding hdev->lock, which serializes the list's writers. After
SMP finds an entry, a concurrent management Remove Remote OOB Data
command can unlink and free it before SMP reads its present flag or
copies its random and confirmation values. Removal can also invalidate
an entry while the lookup is still traversing the list.
KASAN reported:
BUG: KASAN: slab-use-after-free in build_pairing_cmd+0x948/0x9b0
Call Trace:
build_pairing_cmd+0x948/0x9b0
smp_recv_cb+0x459f/0x8110
l2cap_recv_frame+0xf14/0x9190
l2cap_recv_acldata+0xa64/0xd40
hci_rx_work+0x4ca/0x730
Allocated by task 87:
hci_add_remote_oob_data+0x11d/0x530
add_remote_oob_data+0x282/0x400
hci_sock_sendmsg+0x1033/0x1ea0
Freed by task 93:
hci_remote_oob_data_clear+0x108/0x1c0
remove_remote_oob_data+0x198/0x220
hci_sock_sendmsg+0x1033/0x1ea0
Taking hdev->lock in build_pairing_cmd() would recurse for callers that
already hold it and invert the device-to-L2CAP lock order on the receive
path. Add a per-device remote_oob_lock instead, held across the SMP
lookup and copies and by the add, remove and clear helpers. Cover
initialization and in-place updates as well, so SMP cannot read partially
initialized or updated OOB values. Release the mutex on allocation
failure, preserving the existing error return.
The new critical sections acquire no device, connection or channel locks.
Writers retain their existing hdev->lock protection, which continues to
serialize the other readers without changing their locking or behavior. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 02b05bd8b0a632e9a26795bced8f19ca6a5f7079 94afa17d6bfd5c1d367c56c8b63df5f695380861 git |
Not specified |
| CNA |
Linux |
Linux |
affected 02b05bd8b0a632e9a26795bced8f19ca6a5f7079 1e11412a1b9854a89d044576d616675b16141d87 git |
Not specified |
| CNA |
Linux |
Linux |
affected 02b05bd8b0a632e9a26795bced8f19ca6a5f7079 889c61e3d0f1091a958e4b2a24b20bab23d915c4 git |
Not specified |
| CNA |
Linux |
Linux |
affected 02b05bd8b0a632e9a26795bced8f19ca6a5f7079 df5162eeb10e69fe0c2349503882c4a09077f001 git |
Not specified |
| CNA |
Linux |
Linux |
affected 02b05bd8b0a632e9a26795bced8f19ca6a5f7079 81a2345f1984f0b36d3226571bc196316a01b648 git |
Not specified |
| CNA |
Linux |
Linux |
affected 3.19 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 3.19 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.160 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.113 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.56 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.10 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/889c61e3d0f1091a958e4b2a24b20bab23d915c4 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/df5162eeb10e69fe0c2349503882c4a09077f001 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/81a2345f1984f0b36d3226571bc196316a01b648 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/1e11412a1b9854a89d044576d616675b16141d87 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/94afa17d6bfd5c1d367c56c8b63df5f695380861 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.