CVE-2025-21969: Bluetooth: L2CAP: Fix slab-use-after-free Read in l2cap_send_cmd
Bluetooth: L2CAP: Fix slab-use-after-free Read in l2capsendcmd
Affected Software
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.85.1-2 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.20-1 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.1.191 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.84 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.20 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.13.8 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.107-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1 - Compensating control
Add the HCI device lock to the HCI receive-data work queue to synchronize it with the HCI sync command and prevent references to a released l2cap_conn.
Event History
Frequently Asked Questions
What is the severity of CVE-2025-21969?
CVE-2025-21969 is classified as a medium severity vulnerability due to the potential for exploitation through a use-after-free condition.
How do I fix CVE-2025-21969?
To fix CVE-2025-21969, update to the latest patched version of the Linux kernel that addresses this vulnerability.
Which versions of the Linux kernel are affected by CVE-2025-21969?
CVE-2025-21969 affects multiple versions of the Linux kernel prior to the application of the relevant security patches.
What are the potential impacts of CVE-2025-21969?
Exploitation of CVE-2025-21969 could lead to data corruption or system instability due to the improper handling of memory references.
Is CVE-2025-21969 remotely exploitable?
CVE-2025-21969 could potentially be exploited remotely depending on the configuration of the Bluetooth services on the affected systems.