CVE-2023-53762: Bluetooth: hci_sync: Fix UAF in hci_disconnect_all_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.26% (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 5e3ee972f185eb7957ce789b3bf13a3cb790f178, 94d9ba9f9888b748d4abd2aa1547af56ae85f772, a30c074f0b5b7f909a15c978fbc96a29e2f94e42.
Low priority for now. Upgrade to Linux Linux 5e3ee972f185eb7957ce789b3bf13a3cb790f178, 94d9ba9f9888b748d4abd2aa1547af56ae85f772, a30c074f0b5b7f909a15c978fbc96a29e2f94e42 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_disconnect_all_sync Use-after-free can occur in hci_disconnect_all_sync if a connection is deleted by concurrent processing of a controller event. To prevent this the code now tries to iterate over the list backwards to ensure the links are cleanup before its parents, also it no longer relies on a cursor, instead it always uses the last element since hci_abort_conn_sync is guaranteed to call hci_conn_del. UAF crash log: ================================================================== BUG: KASAN: slab-use-after-free in hci_set_powered_sync (net/bluetooth/hci_sync.c:5424) [bluetooth] Read of size 8 at addr ffff888009d9c000 by task kworker/u9:0/124 CPU: 0 PID: 124 Comm: kworker/u9:0 Tainted: G W 6.5.0-rc1+ #10 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-1.fc38 04/01/2014 Workqueue: hci0 hci_cmd_sync_work [bluetooth] Call Trace: <TASK> dump_stack_lvl+0x5b/0x90 print_report+0xcf/0x670 ? __virt_addr_valid+0xdd/0x160 ? hci_set_powered_sync+0x2c9/0x4a0 [bluetooth] kasan_report+0xa6/0xe0 ? hci_set_powered_sync+0x2c9/0x4a0 [bluetooth] ? __pfx_set_powered_sync+0x10/0x10 [bluetooth] hci_set_powered_sync+0x2c9/0x4a0 [bluetooth] ? __pfx_hci_set_powered_sync+0x10/0x10 [bluetooth] ? __pfx_lock_release+0x10/0x10 ? __pfx_set_powered_sync+0x10/0x10 [bluetooth] hci_cmd_sync_work+0x137/0x220 [bluetooth] process_one_work+0x526/0x9d0 ? __pfx_process_one_work+0x10/0x10 ? __pfx_do_raw_spin_lock+0x10/0x10 ? mark_held_locks+0x1a/0x90 worker_thread+0x92/0x630 ? __pfx_worker_thread+0x10/0x10 kthread+0x196/0x1e0 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x2c/0x50 </TASK> Allocated by task 1782: kasan_save_stack+0x33/0x60 kasan_set_track+0x25/0x30 __kasan_kmalloc+0x8f/0xa0 hci_conn_add+0xa5/0xa80 [bluetooth] hci_bind_cis+0x881/0x9b0 [bluetooth] iso_connect_cis+0x121/0x520 [bluetooth] iso_sock_connect+0x3f6/0x790 [bluetooth] __sys_connect+0x109/0x130 __x64_sys_connect+0x40/0x50 do_syscall_64+0x60/0x90 entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Freed by task 695: kasan_save_stack+0x33/0x60 kasan_set_track+0x25/0x30 kasan_save_free_info+0x2b/0x50 __kasan_slab_free+0x10a/0x180 __kmem_cache_free+0x14d/0x2e0 device_release+0x5d/0xf0 kobject_put+0xdf/0x270 hci_disconn_complete_evt+0x274/0x3a0 [bluetooth] hci_event_packet+0x579/0x7e0 [bluetooth] hci_rx_work+0x287/0xaa0 [bluetooth] process_one_work+0x526/0x9d0 worker_thread+0x92/0x630 kthread+0x196/0x1e0 ret_from_fork+0x2c/0x50 ==================================================================
- Published
- Dec 8, 2025
- Updated
- Oct 3, 2026
- EPSS
- 0.2% · 18th percentile
- CWE
- —
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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.
—
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
- 5.17affected
- 182ee45da083db4e3e621541ccf255bfa9652214 and later · before 5e3ee972f185eb7957ce789b3bf13a3cb790f178affected · git
- 182ee45da083db4e3e621541ccf255bfa9652214 and later · before a30c074f0b5b7f909a15c978fbc96a29e2f94e42affected · git
- 182ee45da083db4e3e621541ccf255bfa9652214 and later · before ba3ba53ce1f76fc372b8f918fece4f9b1e41acd4affected · git
- 182ee45da083db4e3e621541ccf255bfa9652214 and later · before 94d9ba9f9888b748d4abd2aa1547af56ae85f772affected · git
- before 5.17not affected · semver
- 6.1.189 and later · up to and including 6.1.*not affected · semver
- 6.4.16 and later · up to and including 6.4.*not affected · semver
- 6.5.3 and later · up to and including 6.5.*not affected · semver
- 6.6 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | bpftool | before 4.18.0-553.105.1.el8_10 | 4.18.0-553.105.1.el8_10 |
| AlmaLinux:8 | kernel | before 4.18.0-553.105.1.el8_10 | 4.18.0-553.105.1.el8_10 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-553.105.1.el8_10 | 4.18.0-553.105.1.el8_10 |
| AlmaLinux:8 | kernel-core | before 4.18.0-553.105.1.el8_10 | 4.18.0-553.105.1.el8_10 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-553.105.1.el8_10 | 4.18.0-553.105.1.el8_10 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-553.105.1.el8_10 | 4.18.0-553.105.1.el8_10 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-553.105.1.el8_10 | 4.18.0-553.105.1.el8_10 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-553.105.1.el8_10 | 4.18.0-553.105.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-553.105.1.el8_10 | 4.18.0-553.105.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-553.105.1.el8_10 | 4.18.0-553.105.1.el8_10 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-553.105.1.el8_10 | 4.18.0-553.105.1.el8_10 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-553.105.1.el8_10 | 4.18.0-553.105.1.el8_10 |
| AlmaLinux:8 | kernel-headers | before 4.18.0-553.105.1.el8_10 | 4.18.0-553.105.1.el8_10 |
| AlmaLinux:8 | kernel-modules | before 4.18.0-553.105.1.el8_10 | 4.18.0-553.105.1.el8_10 |
| AlmaLinux:8 | kernel-modules-extra | before 4.18.0-553.105.1.el8_10 | 4.18.0-553.105.1.el8_10 |
| AlmaLinux:8 | kernel-rt | before 4.18.0-553.105.1.rt7.446.el8_10 | 4.18.0-553.105.1.rt7.446.el8_10 |
| AlmaLinux:8 | kernel-rt-core | before 4.18.0-553.105.1.rt7.446.el8_10 | 4.18.0-553.105.1.rt7.446.el8_10 |
| AlmaLinux:8 | kernel-rt-debug | before 4.18.0-553.105.1.rt7.446.el8_10 | 4.18.0-553.105.1.rt7.446.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-core | before 4.18.0-553.105.1.rt7.446.el8_10 | 4.18.0-553.105.1.rt7.446.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-devel | before 4.18.0-553.105.1.rt7.446.el8_10 | 4.18.0-553.105.1.rt7.446.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules | before 4.18.0-553.105.1.rt7.446.el8_10 | 4.18.0-553.105.1.rt7.446.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | before 4.18.0-553.105.1.rt7.446.el8_10 | 4.18.0-553.105.1.rt7.446.el8_10 |
| AlmaLinux:8 | kernel-rt-devel | before 4.18.0-553.105.1.rt7.446.el8_10 | 4.18.0-553.105.1.rt7.446.el8_10 |
| AlmaLinux:8 | kernel-rt-modules | before 4.18.0-553.105.1.rt7.446.el8_10 | 4.18.0-553.105.1.rt7.446.el8_10 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-53750Dec 8, 2025 · pinctrl: freescale: Fix a memory out of bounds when num_configs is 10Monitor
- ← EarlierCVE-2023-53753Dec 8, 2025 · drm/amd/display: fix mapping to non-allocated address31Monitor
- Later →CVE-2023-53764Dec 8, 2025 · wifi: ath12k: Handle lock during peer_id find35Monitor
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 | 5e3ee972f185eb7957ce789b3bf13a3cb790f178 | Vendor (CNA) |
| Linux Linux | 94d9ba9f9888b748d4abd2aa1547af56ae85f772 | Vendor (CNA) |
| Linux Linux | a30c074f0b5b7f909a15c978fbc96a29e2f94e42 | Vendor (CNA) |
| Linux Linux | ba3ba53ce1f76fc372b8f918fece4f9b1e41acd4 | Vendor (CNA) |
| almalinux:bpftool | 4.18.0-553.105.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-553.105.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 4.18.0-553.105.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-core | 4.18.0-553.105.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-cross-headers | 4.18.0-553.105.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug | 4.18.0-553.105.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-core | 4.18.0-553.105.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-devel | 4.18.0-553.105.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules | 4.18.0-553.105.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules-extra | 4.18.0-553.105.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-devel | 4.18.0-553.105.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-doc | 4.18.0-553.105.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.5.3-1 · Debian:13 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.4.0-150600.23.84.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.4.0-150600.23.84.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-debug | 6.4.0-150600.23.84.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-default | 6.4.0-150600.23.84.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.4.0-150600.23.84.1.150600.12.38.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-docs | 6.4.0-150600.23.84.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.4.0-150600.23.84.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.4.0-150600.23.84.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.4.0-150600.23.84.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-source | 6.4.0-150600.23.84.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-syms | 6.4.0-150600.23.84.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-zfcpdump | 6.4.0-150600.23.84.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
+30
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.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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)
—
CVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.