CVE-2026-98246Bluetooth: hci_sync: Serialize local codec list cleanup
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: Serialize local codec list cleanup hci_dev_close_sync() clears hdev->local_codecs after releasing hdev->lock. Codec list additions and both traversals in sco_sock_getsockopt() use that lock, but the close path does not. A close and BT_CODEC query can therefore interleave as follows: hci_dev_close_sync() sco_sock_getsockopt() hci_dev_lock() fetch codec entry hci_codec_list_clear() kfree(entry) read entry->id The reader then accesses an entry which the close path has freed. KASAN BUG: KASAN: slab-use-after-free in sco_sock_getsockopt+0xfa0/0xfe0 Read of size 1 at addr ffff8881001c3450 Call Trace: sco_sock_getsockopt+0xfa0/0xfe0 do_sock_getsockopt+0x537/0x7b0 __sys_getsockopt+0xf2/0x170 Allocated by task 92: hci_codec_list_add.isra.0+0x2c/0x440 hci_read_codec_capabilities+0x224/0x590 hci_read_supported_codecs+0x2c2/0x640 Freed by task 92: kfree+0x131/0x3c0 hci_codec_list_clear+0xd8/0x160 hci_dev_close_sync+0x92a/0xfa0 Take hdev->lock around the clear operation at its existing point in the close path. This makes the clear wait for active readers and prevents a new traversal until the list is empty without changing teardown ordering.
Timeline
ID reserved
By Linux
- 11 days later
· 11 days later
Published
- 13 days later
· 13 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 626535077ba9dc110787540d1fe24881094c15a1 – < 9f407d52c0d881430d689836d3e7d32aa36f98b5
- affected b938790e70540bf4f2e653dcd74b232494d06c8f – < 560ed4373c06a58123ecdf9ad5ecaddc87a73382
- affected b938790e70540bf4f2e653dcd74b232494d06c8f – < 1ee0c5429dc4a92879bda2554b1bfd4abc6c587c
- affected b938790e70540bf4f2e653dcd74b232494d06c8f – < 4dc1ae5ff75b17e17ec4b74b11cc4b0099e71e00
- affected b938790e70540bf4f2e653dcd74b232494d06c8f – < 1276c2fafd18499769a28f96f45c5a76d6fc990e
- affected b938790e70540bf4f2e653dcd74b232494d06c8f – < 9a10987a2f160a44a638c9a35994ca6e3089696e
- affected eea5a8f0c3b7c884d2351e75fbdd0a3d7def5ae1
- affected 6.1.57 – < 6.1.189
- affected 6.5.7 – < 6.6
- affected 6.6
- unaffected < 6.6
- unaffected 6.1.189 – ≤ 6.1.*
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.112 – ≤ 6.12.*
- unaffected 6.18.54 – ≤ 6.18.*
- unaffected 7.2.8 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/9f407d52c0d881430d689836d3e7d32aa36f98b5 (opens in a new tab)
- https://git.kernel.org/stable/c/560ed4373c06a58123ecdf9ad5ecaddc87a73382 (opens in a new tab)
- https://git.kernel.org/stable/c/1ee0c5429dc4a92879bda2554b1bfd4abc6c587c (opens in a new tab)
- https://git.kernel.org/stable/c/4dc1ae5ff75b17e17ec4b74b11cc4b0099e71e00 (opens in a new tab)
- https://git.kernel.org/stable/c/1276c2fafd18499769a28f96f45c5a76d6fc990e (opens in a new tab)
- https://git.kernel.org/stable/c/9a10987a2f160a44a638c9a35994ca6e3089696e (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-93174 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98246)Record last updated .