CVE-2026-98246: Bluetooth: hci_sync: Serialize local codec list cleanup
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 1276c2fafd18499769a28f96f45c5a76d6fc990e, 1ee0c5429dc4a92879bda2554b1bfd4abc6c587c, 4dc1ae5ff75b17e17ec4b74b11cc4b0099e71e00; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
Low priority for now. Upgrade to Linux Linux 1276c2fafd18499769a28f96f45c5a76d6fc990e, 1ee0c5429dc4a92879bda2554b1bfd4abc6c587c, 4dc1ae5ff75b17e17ec4b74b11cc4b0099e71e00; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 6, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- eea5a8f0c3b7c884d2351e75fbdd0a3d7def5ae1, 6.6affected
- 626535077ba9dc110787540d1fe24881094c15a1 and later · before 9f407d52c0d881430d689836d3e7d32aa36f98b5affected · git
- b938790e70540bf4f2e653dcd74b232494d06c8f and later · before 560ed4373c06a58123ecdf9ad5ecaddc87a73382affected · git
- b938790e70540bf4f2e653dcd74b232494d06c8f and later · before 1ee0c5429dc4a92879bda2554b1bfd4abc6c587caffected · git
- b938790e70540bf4f2e653dcd74b232494d06c8f and later · before 4dc1ae5ff75b17e17ec4b74b11cc4b0099e71e00affected · git
- b938790e70540bf4f2e653dcd74b232494d06c8f and later · before 1276c2fafd18499769a28f96f45c5a76d6fc990eaffected · git
- b938790e70540bf4f2e653dcd74b232494d06c8f and later · before 9a10987a2f160a44a638c9a35994ca6e3089696eaffected · git
- 6.1.57 and later · before 6.1.189affected · semver
- 6.5.7 and later · before 6.6affected · semver
- before 6.6not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.8-1 | 7.2.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98244Oct 6, 2026 · btrfs: clear free space tree creation state on rebuild failure0Monitor
- ← EarlierCVE-2026-98245Oct 6, 2026 · btrfs: take commit root semaphore when iterating in mark_block_group_to_copy()0Monitor
- Later →CVE-2026-98247Oct 6, 2026 · Bluetooth: hci_codec: validate vendor codec count length0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1276c2fafd18499769a28f96f45c5a76d6fc990e | Vendor (CNA) |
| Linux Linux | 1ee0c5429dc4a92879bda2554b1bfd4abc6c587c | Vendor (CNA) |
| Linux Linux | 4dc1ae5ff75b17e17ec4b74b11cc4b0099e71e00 | Vendor (CNA) |
| Linux Linux | 560ed4373c06a58123ecdf9ad5ecaddc87a73382 | Vendor (CNA) |
| Linux Linux | 6.1.189 | Vendor (CNA) |
| Linux Linux | 6.6 | Vendor (CNA) |
| Linux Linux | 9a10987a2f160a44a638c9a35994ca6e3089696e | Vendor (CNA) |
| Linux Linux | 9f407d52c0d881430d689836d3e7d32aa36f98b5 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.8-1 · Debian:14 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 4, 2026+29 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/1ee0c5429dc4a92879bda2554b1bfd4abc6c587c
- git.kernel.org/stable/c/4dc1ae5ff75b17e17ec4b74b11cc4b0099e71e00
- git.kernel.org/stable/c/560ed4373c06a58123ecdf9ad5ecaddc87a73382
- git.kernel.org/stable/c/9a10987a2f160a44a638c9a35994ca6e3089696e
- git.kernel.org/stable/c/9f407d52c0d881430d689836d3e7d32aa36f98b5
Vendor advisories and official records. Exploit/PoC links are deliberately left out.