CVE-2026-98246
Bluetooth: hci_sync: Serialize local codec list cleanup
No known exploitation. EPSS puts it in the 7th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 626535077ba9dc110787540d1fe24881094c15a1, < 9f407d52c0d881430d689836d3e7d32aa36f98b5Upgrade to: 9f407d52c0d881430d689836d3e7d32aa36f98b5Affected: ≥ b938790e70540bf4f2e653dcd74b232494d06c8f, < 560ed4373c06a58123ecdf9ad5ecaddc87a73382Upgrade to: 560ed4373c06a58123ecdf9ad5ecaddc87a73382Affected: ≥ b938790e70540bf4f2e653dcd74b232494d06c8f, < 1ee0c5429dc4a92879bda2554b1bfd4abc6c587cUpgrade to: 1ee0c5429dc4a92879bda2554b1bfd4abc6c587cAffected: ≥ b938790e70540bf4f2e653dcd74b232494d06c8f, < 4dc1ae5ff75b17e17ec4b74b11cc4b0099e71e00Upgrade to: 4dc1ae5ff75b17e17ec4b74b11cc4b0099e71e00 + 5 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 7th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/9f407d52c0d881430d689836d3e7d32aa36f98b5
- git.kernel.org/stable/c/560ed4373c06a58123ecdf9ad5ecaddc87a73382
- git.kernel.org/stable/c/1ee0c5429dc4a92879bda2554b1bfd4abc6c587c
And 3 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI