In the Linux kernel, the following vulnerability has been resolved: Bluetooth: fix UAF in l2cap_sock_cleanup_listen() vs l2cap_conn_del()… (CVE-2026-53357)
A use-after-free (UAF) vulnerability in the Linux kernel's Bluetooth subsystem was resolved. The flaw occurs due to a race condition between socket cleanup and connection deletion functions, leading to use of freed memory. This vulnerability affects the handling of listening sockets and concurrent HCI disconnect events. The issue was identified through KASAN and SMP testing, showing multiple use-after-free reports before the fix. The vulnerability is rated high severity due to its potential impact on confidentiality, integrity, and availability.
AI Analysis
Technical Summary
CVE-2026-53357 is a use-after-free vulnerability in the Linux kernel Bluetooth code, specifically involving the l2cap_sock_cleanup_listen() and l2cap_conn_del() functions. The root cause is a race condition where bt_accept_dequeue() releases a socket without a caller reference, and concurrent HCI disconnect processing frees the socket and its associated channel. Subsequent cleanup attempts use these freed objects, triggering a kernel slab-use-after-free error detected by KASAN. Previous fixes addressed related race conditions but did not cover this specific concurrency scenario. The fix involves taking a reference on the socket before releasing it and carefully managing locks to prevent use-after-free during concurrent socket and channel cleanup.
Potential Impact
Successful exploitation could lead to use-after-free conditions in kernel memory, potentially causing system crashes or allowing an attacker with limited privileges to execute arbitrary code or escalate privileges. The CVSS vector indicates high impact on confidentiality, integrity, and availability. However, no known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid unprivileged concurrent operations involving Bluetooth listening sockets and HCI disconnects. Monitor vendor channels for updates and apply patches promptly once released.
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: fix UAF in l2cap_sock_cleanup_listen() vs l2cap_conn_del()… (CVE-2026-53357)
Description
A use-after-free (UAF) vulnerability in the Linux kernel's Bluetooth subsystem was resolved. The flaw occurs due to a race condition between socket cleanup and connection deletion functions, leading to use of freed memory. This vulnerability affects the handling of listening sockets and concurrent HCI disconnect events. The issue was identified through KASAN and SMP testing, showing multiple use-after-free reports before the fix. The vulnerability is rated high severity due to its potential impact on confidentiality, integrity, and availability.
CVSS v3.1
Score 8.0high
Affected software
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-53357 is a use-after-free vulnerability in the Linux kernel Bluetooth code, specifically involving the l2cap_sock_cleanup_listen() and l2cap_conn_del() functions. The root cause is a race condition where bt_accept_dequeue() releases a socket without a caller reference, and concurrent HCI disconnect processing frees the socket and its associated channel. Subsequent cleanup attempts use these freed objects, triggering a kernel slab-use-after-free error detected by KASAN. Previous fixes addressed related race conditions but did not cover this specific concurrency scenario. The fix involves taking a reference on the socket before releasing it and carefully managing locks to prevent use-after-free during concurrent socket and channel cleanup.
Potential Impact
Successful exploitation could lead to use-after-free conditions in kernel memory, potentially causing system crashes or allowing an attacker with limited privileges to execute arbitrary code or escalate privileges. The CVSS vector indicates high impact on confidentiality, integrity, and availability. However, no known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid unprivileged concurrent operations involving Bluetooth listening sockets and HCI disconnects. Monitor vendor channels for updates and apply patches promptly once released.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-mf4h-hfv8-f4v4
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-53357"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- 3.1
Threat ID: 6a46ecd727e9c7971943f52a
Added to database: 07/02/2026, 22:57:27 UTC
Last enriched: 07/19/2026, 01:22:35 UTC
Last updated: 07/31/2026, 19:24:47 UTC
Views: 40
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.