A race condition in the Linux kernel Bluetooth L2CAP implementation permits a use-after-free vulnerability, which may be leveraged by a local or adjacent attacker to impact system integrity.

This is a race condition vulnerability within the Bluetooth L2CAP module, specifically occurring during socket teardown. An attacker with low privileges can trigger a use-after-free condition by racing the connection callback against the parent socket cleanup process.

Successful exploitation of this flaw allows an attacker to manipulate memory management, potentially leading to unauthorized code execution or denial of service. With a CVSS score of 8.0, this high-severity vulnerability poses a significant risk to the stability and confidentiality of impacted systems, especially those utilizing Bluetooth connectivity in exposed environments.

Immediate Action: Update the Linux kernel to version 6.1.188, 6.6.157, 6.12.110, 6.18.52, or a later stable release provided by your distribution vendor.

Proactive Monitoring: Review system logs for kernel panics or repeated Bluetooth service failures that may indicate an exploitation attempt.

Compensating Controls: If patching is not immediately feasible, disable the Bluetooth service if it is not required for system operations to eliminate the attack surface.

Public Exploit Available: No

Given the potential for code execution and the core nature of the affected component, organizations should prioritize kernel updates as part of their standard patch management cycle. Validate the installation of the corrected kernel versions across all affected infrastructure to neutralize this high-severity risk.