GHSA-G43C-XVH2-VXH2
Vulnerability from github – Published: 2026-10-18 18:32 – Updated: 2026-10-21 15:41In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_sync: Fix inquiry cache use-after-free
The sync command worker holds hdev->req_lock, but inquiry-cache updates and flushes use hdev->lock. Both hci_acl_create_conn_sync() and hci_stop_discovery_sync() look up entries and read their fields without taking hdev->lock.
After either lookup returns, a concurrent HCIINQUIRY ioctl can acquire hdev->lock and flush the cache, freeing the entry. The worker then reads the freed entry while preparing a create-connection or remote-name-cancel command. The list traversal also races with cache updates and removal.
KASAN reported these accesses:
BUG: KASAN: slab-use-after-free in hci_acl_create_conn_sync+0x5f1/0x650 Workqueue: hci0 hci_cmd_sync_work Call Trace: hci_acl_create_conn_sync+0x5f1/0x650 hci_cmd_sync_work+0x13c/0x290
Allocated by task 90: hci_inquiry_cache_update+0x3e6/0x7d0 hci_inquiry_result_evt+0x3cb/0x560
Freed by task 93: hci_inquiry_cache_flush+0x111/0x2b0 hci_inquiry+0x2f2/0x780 hci_sock_ioctl+0x269/0x5f0
BUG: KASAN: slab-use-after-free in hci_stop_discovery_sync+0x3b1/0x3c0 Workqueue: hci0 hci_cmd_sync_work Call Trace: hci_stop_discovery_sync+0x3b1/0x3c0 hci_cmd_sync_work+0x173/0x300
Allocated by task 86: hci_inquiry_cache_update+0x483/0x940 hci_inquiry_result_evt+0x3cb/0x560
Freed by task 91: hci_inquiry_cache_flush+0x13e/0x2f0 hci_inquiry+0x2f2/0x780 hci_sock_ioctl+0x269/0x5f0
Hold hdev->lock across each lookup and all reads from its result. Copy the remote address before unlocking so discovery cancellation does not retain a cache entry pointer. Release the lock before sending synchronous HCI commands, since their completion handlers may need the same lock.
{
"affected": [],
"aliases": [
"CVE-2026-98737"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-18T16:17:27Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sync: Fix inquiry cache use-after-free\n\nThe sync command worker holds hdev-\u003ereq_lock, but inquiry-cache updates\nand flushes use hdev-\u003elock. Both hci_acl_create_conn_sync() and\nhci_stop_discovery_sync() look up entries and read their fields without\ntaking hdev-\u003elock.\n\nAfter either lookup returns, a concurrent HCIINQUIRY ioctl can acquire\nhdev-\u003elock and flush the cache, freeing the entry. The worker then reads\nthe freed entry while preparing a create-connection or remote-name-cancel\ncommand. The list traversal also races with cache updates and removal.\n\nKASAN reported these accesses:\n\n BUG: KASAN: slab-use-after-free in hci_acl_create_conn_sync+0x5f1/0x650\n Workqueue: hci0 hci_cmd_sync_work\n Call Trace:\n hci_acl_create_conn_sync+0x5f1/0x650\n hci_cmd_sync_work+0x13c/0x290\n\n Allocated by task 90:\n hci_inquiry_cache_update+0x3e6/0x7d0\n hci_inquiry_result_evt+0x3cb/0x560\n\n Freed by task 93:\n hci_inquiry_cache_flush+0x111/0x2b0\n hci_inquiry+0x2f2/0x780\n hci_sock_ioctl+0x269/0x5f0\n\n BUG: KASAN: slab-use-after-free in hci_stop_discovery_sync+0x3b1/0x3c0\n Workqueue: hci0 hci_cmd_sync_work\n Call Trace:\n hci_stop_discovery_sync+0x3b1/0x3c0\n hci_cmd_sync_work+0x173/0x300\n\n Allocated by task 86:\n hci_inquiry_cache_update+0x483/0x940\n hci_inquiry_result_evt+0x3cb/0x560\n\n Freed by task 91:\n hci_inquiry_cache_flush+0x13e/0x2f0\n hci_inquiry+0x2f2/0x780\n hci_sock_ioctl+0x269/0x5f0\n\nHold hdev-\u003elock across each lookup and all reads from its result. Copy the\nremote address before unlocking so discovery cancellation does not retain\na cache entry pointer. Release the lock before sending synchronous HCI\ncommands, since their completion handlers may need the same lock.",
"id": "GHSA-g43c-xvh2-vxh2",
"modified": "2026-10-21T15:41:56Z",
"published": "2026-10-18T18:32:01Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98737"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/333257e6e4a7bcaaea82fd357121d0f1e6b76c7b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/52edf1c0e59dea37b8368c4a2559dca96b2fdfea"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8ed67535fdff40ca652bcd4ac7da68d11d01bd34"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a642f498f0b08f2aa9f4a69468db92f57a72349d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ddc9edb244cc8b5266595e8fc220e7813f2b603a"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.
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…
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.
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.