CVE-2026-53357: Bluetooth: fix UAF in l2cap_sock_cleanup_listen() vs l2cap_conn_del()
Noroxi assessment
Priority: Monitor (action score 32/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. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 407217734835d21d4e0105ebf347860dc1806f88, 5d86d2f1b4d9a508c441d3e45277ae1a73cfed57, 751de6ec671fe75ad9cf65a0638d2a06b6a5984d; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.143.1-1.
Low priority for now. Upgrade to Linux Linux 407217734835d21d4e0105ebf347860dc1806f88, 5d86d2f1b4d9a508c441d3e45277ae1a73cfed57, 751de6ec671fe75ad9cf65a0638d2a06b6a5984d; azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 6.6.143.1-1 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: fix UAF in l2cap_sock_cleanup_listen() vs l2cap_conn_del() bt_accept_dequeue() unlinks a not-yet-accepted child from the parent accept queue and release_sock()s it before returning, so the returned sk has no caller reference and is unlocked. l2cap_sock_cleanup_listen() walks these children on listening-socket close. A concurrent HCI disconnect drives hci_rx_work -> l2cap_conn_del() which runs l2cap_chan_del() + l2cap_sock_kill() and frees the child sk and its l2cap_chan; cleanup_listen() then uses both: BUG: KASAN: slab-use-after-free in l2cap_sock_kill l2cap_sock_kill / l2cap_sock_cleanup_listen / __x64_sys_close Freed by: l2cap_conn_del -> l2cap_sock_close_cb -> l2cap_sock_kill This is distinct from the two fixes already in this area: commit e83f5e24da741 ("Bluetooth: serialize accept_q access") serialises the accept_q list/poll and takes temporary refs inside bt_accept_dequeue(), and CVE-2025-39860 serialises the userspace close()/accept() race by calling cleanup_listen() under lock_sock() in l2cap_sock_release(). Neither covers l2cap_conn_del() running from hci_rx_work, so this UAF still reproduces on current bluetooth/master. Take the reference at the source: bt_accept_dequeue() does sock_hold() while sk is still locked, before release_sock(); callers sock_put(). cleanup_listen() pins the chan with l2cap_chan_hold_unless_zero() under a brief child sk lock (serialising vs l2cap_sock_teardown_cb()), drops it before l2cap_chan_lock(), and skips a duplicate l2cap_sock_kill() on SOCK_DEAD. conn->lock is not taken here: cleanup_listen() runs under the parent sk lock and that would invert conn->lock -> chan->lock -> sk_lock (lockdep). KASAN/SMP: an unprivileged listen/close vs HCI-disconnect race produced 12 use-after-free reports per run before this change; 0, and no lockdep report, over 1600+ raced iterations after it on bluetooth/master.
- Published
- Jul 2, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.3% · 26th percentile
- CWE
- CWE-416
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.0 / 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.0
- 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.7 and later · before 5.10.259
- linux linux kernel5.11 and later · before 5.15.210
- linux linux kernel5.16 and later · before 6.1.175
- linux linux kernel6.2 and later · before 6.6.142
- linux linux kernel6.7 and later · before 6.12.92
- linux linux kernel6.13 and later · before 6.18.34
- linux linux kernel6.19 and later · before 7.0.11
- linux linux kernel7.1
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.7affected
- 15f02b91056253e8cdc592888f431da0731337b8 and later · before 751de6ec671fe75ad9cf65a0638d2a06b6a5984daffected · git
- 15f02b91056253e8cdc592888f431da0731337b8 and later · before 407217734835d21d4e0105ebf347860dc1806f88affected · git
- 15f02b91056253e8cdc592888f431da0731337b8 and later · before 7eebd4c2c86f573af87ff165d08a83432eb0b919affected · git
- 15f02b91056253e8cdc592888f431da0731337b8 and later · before 5d86d2f1b4d9a508c441d3e45277ae1a73cfed57affected · git
- 15f02b91056253e8cdc592888f431da0731337b8 and later · before 87c543e2f78d0871f271df92dab98901bbd5b6f5affected · git
- 15f02b91056253e8cdc592888f431da0731337b8 and later · before added1213395071470a900cc845a042fb51882a6affected · git
- 15f02b91056253e8cdc592888f431da0731337b8 and later · before a5ca86a6097a8b030ca3226cd300b17ed330f966affected · git
- 15f02b91056253e8cdc592888f431da0731337b8 and later · before ab1513597c6cf17cd1ad2a21e3b045421b48e022affected · git
- before 5.7not affected · semver
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.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.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-53354Jul 1, 2026 · arm64: errata: Mitigate TLBI errata on various Arm CPUs35Monitor
- ← EarlierCVE-2026-53356Jul 1, 2026 · drm/i915/gem: Fix phys BO pread/pwrite with offset31Monitor
- Later →CVE-2026-53358Jul 2, 2026 · Bluetooth: L2CAP: use chan timer to close channels in cleanup_listen()35Monitor
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 | 407217734835d21d4e0105ebf347860dc1806f88 | Vendor (CNA) |
| Linux Linux | 5d86d2f1b4d9a508c441d3e45277ae1a73cfed57 | Vendor (CNA) |
| Linux Linux | 751de6ec671fe75ad9cf65a0638d2a06b6a5984d | Vendor (CNA) |
| Linux Linux | 7eebd4c2c86f573af87ff165d08a83432eb0b919 | Vendor (CNA) |
| Linux Linux | 87c543e2f78d0871f271df92dab98901bbd5b6f5 | Vendor (CNA) |
| Linux Linux | a5ca86a6097a8b030ca3226cd300b17ed330f966 | Vendor (CNA) |
| Linux Linux | ab1513597c6cf17cd1ad2a21e3b045421b48e022 | Vendor (CNA) |
| Linux Linux | added1213395071470a900cc845a042fb51882a6 | Vendor (CNA) |
| azl3 kernel 6.6.139.1-1 on Azure Linux 3.0 | 6.6.143.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:kernel | 6.12.0-211.63.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k | 6.12.0-211.63.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-core | 6.12.0-211.63.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 6.12.0-211.63.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 6.12.0-211.63.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 6.12.0-211.63.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 6.12.0-211.63.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 6.12.0-211.63.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 6.12.0-211.63.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 6.12.0-211.63.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 6.12.0-211.63.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 6.12.0-211.63.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.1.176-1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-687.55.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-687.55.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-687.55.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-687.55.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-687.55.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-687.55.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-687.55.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-687.55.1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
+4
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.
- A low-privileged account is enough.
- 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
- Low
- 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:L/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
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/5d86d2f1b4d9a508c441d3e45277ae1a73cfed57
- git.kernel.org/stable/c/751de6ec671fe75ad9cf65a0638d2a06b6a5984d
- git.kernel.org/stable/c/7eebd4c2c86f573af87ff165d08a83432eb0b919
- git.kernel.org/stable/c/87c543e2f78d0871f271df92dab98901bbd5b6f5
- git.kernel.org/stable/c/a5ca86a6097a8b030ca3226cd300b17ed330f966
- git.kernel.org/stable/c/ab1513597c6cf17cd1ad2a21e3b045421b48e022
- git.kernel.org/stable/c/added1213395071470a900cc845a042fb51882a6
Vendor advisories and official records. Exploit/PoC links are deliberately left out.