CVE-2026-63944: Bluetooth: hci_sync: fix UAF in hci_le_create_cis_sync
Noroxi assessment
Priority: Monitor (action score 35/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.33% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 380e67b1794a9a281a0cb592b4e62077fbd0c8ca, a55618c0f4cead9e59c63f5ee030d393fd70d861, a921957d39290143629eb38c4f74b9bef8035d0a.
Low priority for now. Upgrade to Linux Linux 380e67b1794a9a281a0cb592b4e62077fbd0c8ca, a55618c0f4cead9e59c63f5ee030d393fd70d861, a921957d39290143629eb38c4f74b9bef8035d0a 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: 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).
- ALSA-2026:65334
- RHSA-2026:65334
- RLSA-2026:65334
- SUSE-SU-2026:23997-1
- SUSE-SU-2026:23998-1
- SUSE-SU-2026:23999-1
- SUSE-SU-2026:24000-1
- SUSE-SU-2026:24001-1
- SUSE-SU-2026:24002-1
- SUSE-SU-2026:24003-1
- SUSE-SU-2026:24004-1
- SUSE-SU-2026:24005-1
- SUSE-SU-2026:24006-1
- SUSE-SU-2026:24007-1
- SUSE-SU-2026:24008-1
- SUSE-SU-2026:24009-1
- SUSE-SU-2026:24022-1
- SUSE-SU-2026:24023-1
- SUSE-SU-2026:24024-1
- SUSE-SU-2026:24025-1
- Published
- Jul 19, 2026
- Updated
- Oct 26, 2026
- EPSS
- 0.3% · 27th percentile
- CWE
- CWE-416
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Is your version affected? Check itNoroxi 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
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
- 6.4affected
- c09b80be6ffc338634b2f5f8cfa12b6843410834 and later · before a55618c0f4cead9e59c63f5ee030d393fd70d861affected · git
- c09b80be6ffc338634b2f5f8cfa12b6843410834 and later · before a921957d39290143629eb38c4f74b9bef8035d0aaffected · git
- c09b80be6ffc338634b2f5f8cfa12b6843410834 and later · before d9019210c8c30d40eb20094274cc647e352f48f7affected · git
- c09b80be6ffc338634b2f5f8cfa12b6843410834 and later · before 380e67b1794a9a281a0cb592b4e62077fbd0c8caaffected · git
- c09b80be6ffc338634b2f5f8cfa12b6843410834 and later · before bfea6091e0fffb270c20e74384b660910277eb6caffected · git
- before 6.4not affected · semver
- 6.6.143 and later · up to and including 6.6.*not affected · semver
- 6.12.93 and later · up to and including 6.12.*not affected · semver
- 6.18.35 and later · up to and including 6.18.*not affected · semver
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.4 and later · before 6.6.143
- linux linux kernel6.7 and later · before 6.12.93
- linux linux kernel6.13 and later · before 6.18.35
- linux linux kernel6.19 and later · before 7.0.12
- linux linux kernel7.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-63942Jul 19, 2026 · parport: Fix race between port and client registration31Monitor
- ← EarlierCVE-2026-63943Jul 19, 2026 · Input: xpad - fix out-of-bounds access for Share button28Monitor
- Later →CVE-2026-63945Jul 19, 2026 · Bluetooth: ISO: serialize iso_sock_clear_timer with socket lock31Monitor
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 | 380e67b1794a9a281a0cb592b4e62077fbd0c8ca | Vendor (CNA) |
| Linux Linux | a55618c0f4cead9e59c63f5ee030d393fd70d861 | Vendor (CNA) |
| Linux Linux | a921957d39290143629eb38c4f74b9bef8035d0a | Vendor (CNA) |
| Linux Linux | bfea6091e0fffb270c20e74384b660910277eb6c | Vendor (CNA) |
| Linux Linux | d9019210c8c30d40eb20094274cc647e352f48f7 | Vendor (CNA) |
| almalinux:kernel | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-core | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.12.94-1 · Debian:13 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debuginfo-common-ppc64le | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
+20
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.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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 (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.