CVE-2026-98733Bluetooth: hci_core: Serialize fragmented ISO packet queueing
- —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_core: Serialize fragmented ISO packet queueing The fragmented path in hci_queue_iso() calls __skb_queue_tail() without holding conn->data_q.lock. The socket lock serializes senders, but the transmit worker can concurrently remove packets from this queue using skb_dequeue(). After an insertion saves the old tail pointer, hci_sched_iso() can dequeue that packet and pass it to the driver. The driver can free the packet before the insertion resumes and writes to the old tail's next pointer, causing a use-after-free. Concurrent updates can also corrupt the queue. KASAN reported: BUG: KASAN: slab-use-after-free in hci_send_iso+0xc7d/0xe10 Call Trace: hci_send_iso+0xc7d/0xe10 iso_sock_sendmsg+0x710/0x900 __sys_sendto+0x34a/0x3a0 Allocated by task 86: __alloc_skb+0xdd/0x820 alloc_skb_with_frags+0x7e/0x770 sock_alloc_send_pskb+0x67a/0x820 bt_skb_sendmsg.constprop.0+0xc0/0x6c0 iso_sock_sendmsg+0x44e/0x900 Freed by task 90: kmem_cache_free+0xcb/0x3d0 vhci_read+0x33f/0x4d0 vfs_read+0x177/0xa20 Hold the queue lock across the entire fragment batch, as hci_queue_acl() does, to serialize insertion against dequeue while preserving fragment ordering.
Timeline
ID reserved
By Linux
- 23 days later
· 23 days later
Published
- 12 days later
· 12 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 (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 26afbd826ee326e63a334c37fd45e82e50a615ec – < e328b5823fa6b0b160d0922d6d68323e910d09a4
- affected 26afbd826ee326e63a334c37fd45e82e50a615ec – < 545fa70f730eb648a610a2f4b2d270865f77b619
- affected 26afbd826ee326e63a334c37fd45e82e50a615ec – < d6d709981208567868c5c01ebd1bec5e5e7fdab0
- affected 26afbd826ee326e63a334c37fd45e82e50a615ec – < 708cdd203d0bbcf9255fffb2e4c308d5b28851a7
- affected 26afbd826ee326e63a334c37fd45e82e50a615ec – < a7161730a3ab3f0a3896000db7ab0284683936e6
- affected 26afbd826ee326e63a334c37fd45e82e50a615ec – < 1a572db43c057566771b485598ad2e66cb390821
- affected 6.0
- unaffected < 6.0
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.113 – ≤ 6.12.*
- unaffected 6.18.56 – ≤ 6.18.*
- unaffected 7.2.10 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/e328b5823fa6b0b160d0922d6d68323e910d09a4 (opens in a new tab)
- https://git.kernel.org/stable/c/545fa70f730eb648a610a2f4b2d270865f77b619 (opens in a new tab)
- https://git.kernel.org/stable/c/d6d709981208567868c5c01ebd1bec5e5e7fdab0 (opens in a new tab)
- https://git.kernel.org/stable/c/708cdd203d0bbcf9255fffb2e4c308d5b28851a7 (opens in a new tab)
- https://git.kernel.org/stable/c/a7161730a3ab3f0a3896000db7ab0284683936e6 (opens in a new tab)
- https://git.kernel.org/stable/c/1a572db43c057566771b485598ad2e66cb390821 (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-103818 (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-98733)Record last updated .