Accessing the ISO socket pointer in the Bluetooth ISO subsystem without acquiring the necessary lock creates a race condition that can cause a null or stale dereference, leading to a kernel fault and system crash. The CVE does not provide evidence of privilege escalation; its primary effect is the loss of availability due to a kernel panic triggered during a Bluetooth ISO connection attempt.

Linux kernel releases that include the Bluetooth ISO code before the commit that added lock_sock in iso_connect_ind remain affected. The change is present in recent kernel updates; older or custom builds that have not applied the patch are vulnerable.

The CVSS score of 8.8 indicates high severity. The EPSS score of <1% suggests low current exploitation probability, and the vulnerability is not listed in the CISA KEV catalog. The attack vector is not explicitly documented; it may be local or could potentially be remote if an attacker can trigger a Bluetooth ISO connection with sufficient proximity. The required race condition and the need to manipulate the Bluetooth stack make exploitation more complex, yielding a moderate risk of successful attack but high impact if the fault occurs.