CVE-2026-53357: Bluetooth: fix UAF in l2cap_sock_cleanup_listen() vs l2cap_conn_del()
Published Jul 2, 2026
·Updated
Bluetooth: fix UAF in l2capsockcleanuplisten() vs l2capconndel()
Affected Software
13 affected componentsFixes available
Linux kernel Bluetooth L2CAP
Microsoft azl3 kernel 6.6.139.1-1<6.6.143.1-1
6.6.143.1-1
Linux Linux kernel>=5.7<5.10.259
Linux Linux kernel>=5.11<5.15.210
Linux Linux kernel>=5.16<6.1.175
Linux Linux kernel>=6.2<6.6.142
Linux Linux kernel>=6.7<6.12.92
Linux Linux kernel>=6.13<6.18.34
Linux Linux kernel>=6.19<7.0.11
Linux Linux kernel=7.1-rc1
Linux Linux kernel=7.1-rc2
Linux Linux kernel=7.1-rc3
Linux Linux kernel=7.1-rc4
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.143.1-1
Event History
Jul 2, 2026
CVE Published
via MITRE·01:43 PM
Data Sourced
via MITRE·01:43 PM
DescriptionSeverity
Data Sourced
via NVD·03:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jul 3, 2026
Data Sourced
via Microsoft·08:02 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:02 AM
Affected Software
Updated
via Microsoft·08:02 AM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2026-53357?
The severity of CVE-2026-53357 is rated at 53.
2
How do I fix CVE-2026-53357?
To fix CVE-2026-53357, update your Linux kernel to the latest version that contains the patch addressing this vulnerability.
3
What types of systems are affected by CVE-2026-53357?
CVE-2026-53357 affects systems running the Linux kernel Bluetooth L2CAP implementation.
4
What is the nature of the vulnerability in CVE-2026-53357?
CVE-2026-53357 is a use-after-free vulnerability occurring in the l2cap_sock_cleanup_listen() and l2cap_conn_del() functions.
5
Can CVE-2026-53357 lead to remote code execution?
Yes, CVE-2026-53357 has the potential to lead to remote code execution due to improper handling of socket connections.