FKIE_CVE-2026-98734
Vulnerability from fkie_nvd - Published: 2026-10-18 16:17 - Updated: 2026-10-21 13:21
Severity
Summary
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_core: Serialize SCO and ISO scheduling with teardown
hci_low_sent() selects a connection under RCU but drops the read lock
before calculating its quota and returning it to the scheduler. The
connection is then used without lifetime protection by hci_sched_iso()
and hci_sched_sco().
After the TX worker drops the RCU read lock, hci_abort_conn_sync() on
hdev->req_workqueue can remove the connection from the hash, complete
synchronize_rcu(), purge its queues and release it. The TX worker on
hdev->workqueue can then access the freed connection in hci_quote_sent()
or while dequeuing packets and updating conn->sent.
KASAN reported:
BUG: KASAN: slab-use-after-free in hci_low_sent+0x730/0x840
Workqueue: hci0 hci_tx_work
Call Trace:
hci_low_sent+0x730/0x840
hci_sched_iso+0x25e/0x4d0
hci_tx_work+0x239/0xcb0
Allocated by task 93:
__hci_conn_add+0x16f/0x1b40
hci_bind_bis+0x782/0x17b0
hci_connect_bis+0xa0/0x510
iso_sock_connect+0x589/0x1050
Freed by task 88:
kfree+0x131/0x3c0
device_release+0xc8/0x240
kobject_put+0x14d/0x280
hci_conn_del+0x55a/0xe80
hci_disconnect_sync+0x156/0x180
hci_abort_conn_sync+0x3e7/0x940
hci_cmd_sync_work+0x13c/0x290
Hold hci_dev_lock() across connection selection and transmission in both
SCO and ISO scheduling, serializing them with connection teardown. This
also prevents queuing completion timestamps after the connection queues
have been purged. Extending RCU across transmission would be unsafe
because the transmit path can sleep. Keep the ISO timeout check outside
the mutex since hci_link_tx_to() takes it itself.
The preceding channel fix already holds this mutex in the ACL and LE
schedulers, which call the SCO scheduler between packets. Move the SCO
body to __hci_sched_sco(), assert that its caller holds the mutex, and
use it directly from these locked paths. Keep a locking hci_sched_sco()
wrapper for the direct calls from hci_tx_work(). This avoids recursively
acquiring the device mutex while preserving the scheduling order.
Remove the obsolete claim that connection removal disables TX.
References
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"net/bluetooth/hci_core.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "f997e03e2ef58aa7114828c9d924e515a9a1db9c",
"status": "affected",
"version": "bf4c63252490ba78fb833cc7acf1a5b1900c970f",
"versionType": "git"
},
{
"lessThan": "101825c09ad6b7daa6cf4c9e6b1720b13de15596",
"status": "affected",
"version": "bf4c63252490ba78fb833cc7acf1a5b1900c970f",
"versionType": "git"
},
{
"lessThan": "1681f97afdf92e8557f2f3118ddc898471b5d299",
"status": "affected",
"version": "bf4c63252490ba78fb833cc7acf1a5b1900c970f",
"versionType": "git"
},
{
"lessThan": "ecdb1c66d8e14e63731c52d6fbcfa604064913c4",
"status": "affected",
"version": "bf4c63252490ba78fb833cc7acf1a5b1900c970f",
"versionType": "git"
},
{
"lessThan": "848a7a91c7f03675d3bd8db6f7721cbf9cb50e21",
"status": "affected",
"version": "bf4c63252490ba78fb833cc7acf1a5b1900c970f",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"net/bluetooth/hci_core.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "3.3"
},
{
"lessThan": "3.3",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.160",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.113",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.56",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.10",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_core: Serialize SCO and ISO scheduling with teardown\n\nhci_low_sent() selects a connection under RCU but drops the read lock\nbefore calculating its quota and returning it to the scheduler. The\nconnection is then used without lifetime protection by hci_sched_iso()\nand hci_sched_sco().\n\nAfter the TX worker drops the RCU read lock, hci_abort_conn_sync() on\nhdev-\u003ereq_workqueue can remove the connection from the hash, complete\nsynchronize_rcu(), purge its queues and release it. The TX worker on\nhdev-\u003eworkqueue can then access the freed connection in hci_quote_sent()\nor while dequeuing packets and updating conn-\u003esent.\n\nKASAN reported:\n\n BUG: KASAN: slab-use-after-free in hci_low_sent+0x730/0x840\n Workqueue: hci0 hci_tx_work\n Call Trace:\n hci_low_sent+0x730/0x840\n hci_sched_iso+0x25e/0x4d0\n hci_tx_work+0x239/0xcb0\n\n Allocated by task 93:\n __hci_conn_add+0x16f/0x1b40\n hci_bind_bis+0x782/0x17b0\n hci_connect_bis+0xa0/0x510\n iso_sock_connect+0x589/0x1050\n\n Freed by task 88:\n kfree+0x131/0x3c0\n device_release+0xc8/0x240\n kobject_put+0x14d/0x280\n hci_conn_del+0x55a/0xe80\n hci_disconnect_sync+0x156/0x180\n hci_abort_conn_sync+0x3e7/0x940\n hci_cmd_sync_work+0x13c/0x290\n\nHold hci_dev_lock() across connection selection and transmission in both\nSCO and ISO scheduling, serializing them with connection teardown. This\nalso prevents queuing completion timestamps after the connection queues\nhave been purged. Extending RCU across transmission would be unsafe\nbecause the transmit path can sleep. Keep the ISO timeout check outside\nthe mutex since hci_link_tx_to() takes it itself.\n\nThe preceding channel fix already holds this mutex in the ACL and LE\nschedulers, which call the SCO scheduler between packets. Move the SCO\nbody to __hci_sched_sco(), assert that its caller holds the mutex, and\nuse it directly from these locked paths. Keep a locking hci_sched_sco()\nwrapper for the direct calls from hci_tx_work(). This avoids recursively\nacquiring the device mutex while preserving the scheduling order.\n\nRemove the obsolete claim that connection removal disables TX."
}
],
"id": "CVE-2026-98734",
"lastModified": "2026-10-21T13:21:40.570",
"metrics": {},
"published": "2026-10-18T16:17:27.010",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/101825c09ad6b7daa6cf4c9e6b1720b13de15596"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/1681f97afdf92e8557f2f3118ddc898471b5d299"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/848a7a91c7f03675d3bd8db6f7721cbf9cb50e21"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/ecdb1c66d8e14e63731c52d6fbcfa604064913c4"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/f997e03e2ef58aa7114828c9d924e515a9a1db9c"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Loading…
Loading…
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.