CVE-2026-63944
What it is
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: fix UAF in hci_le_create_cis_sync hci_le_create_cis_sync() dereferences conn->conn_timeout after releasing both rcu_read_lock() and hci_dev_lock(hdev). The conn pointer was obtained from an RCU-protected iteration over hdev->conn_hash.list and is not valid once these locks are dropped. A concurrent disconnect can free the hci_conn between the unlock and the dereference, causing a use-after-free read. The cancellation mechanism in hci_conn_del() cannot prevent this because hci_le_create_cis_pending() queues hci_create_cis_sync with data=NULL: hci_cmd_sync_queue(hdev, hci_create_cis_sync, NULL, NULL); While hci_conn_del() dequeues with data=conn: hci_cmd_sync_dequeue(hdev, NULL, conn, NULL); Since NULL != conn, the lookup in _hci_cmd_sync_lookup_entry() never matches, and the pending work item is not cancelled. Fix this by saving conn->conn_timeout into a local variable while the locks are still held, so the stale conn pointer is never dereferenced after unlock. This is the same class of bug as the one fixed by commit 035c25007c9e ("Bluetooth: hci_sync: Fix UAF on le_read_features_complete") which addressed the identical pattern in a different function. This vulnerability was identified using 0sec.ai, an open-source automated security auditing platform (https://github.com/0sec-labs).
At a glance
- Exploitability
- Can be exploited from the same network segment without logging in. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 8.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Weakness
- CWE-416 · Use after free
- Record status
- Analyzed
Affected
- Linux Kernel < 6.6.143
- Linux Kernel < 6.12.93
- Linux Kernel < 6.18.35
- Linux Kernel < 7.0.12
- Linux Kernel 7.1
Attack profile CVSS 3.1 · 8.8
- Attack vector
- Adjacent network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-63944.md and follow it. Check whether this project is affected by CVE-2026-63944. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/380e67b1794a9a281a0cb592b4e62077fbd0c8ca
- https://git.kernel.org/stable/c/a55618c0f4cead9e59c63f5ee030d393fd70d861
- https://git.kernel.org/stable/c/a921957d39290143629eb38c4f74b9bef8035d0a
- https://git.kernel.org/stable/c/bfea6091e0fffb270c20e74384b660910277eb6c
- https://git.kernel.org/stable/c/d9019210c8c30d40eb20094274cc647e352f48f7
References
- https://git.kernel.org/stable/c/380e67b1794a9a281a0cb592b4e62077fbd0c8ca
- https://git.kernel.org/stable/c/a55618c0f4cead9e59c63f5ee030d393fd70d861
- https://git.kernel.org/stable/c/a921957d39290143629eb38c4f74b9bef8035d0a
- https://git.kernel.org/stable/c/bfea6091e0fffb270c20e74384b660910277eb6c
- https://git.kernel.org/stable/c/d9019210c8c30d40eb20094274cc647e352f48f7