Impact
A flaw in the Linux kernel’s Bluetooth L2CAP subsystem can trigger a kernel panic when an attacker sends a specially crafted packet that includes a destination channel identifier (dcid) that conflicts with an already assigned channel. The bug stems from an improper use of a list cursor during channel deletion or cloning, which can result in a use‑after‑free or memory corruption (CWE-416, CWE-667). The crash prevents system functionality, providing attackers only a denial‑of‑service without direct impact on confidentiality or integrity.
Affected Systems
All Linux kernels that ship the unpatched Bluetooth L2CAP code are affected. This includes every distribution that has not yet applied the upstream patch; it applies to the generic kernel and all release candidates under development until a vendor releases a secured kernel update.
Risk and Exploitability
The CVSS base score of 8.8 indicates a high‑risk vulnerability, while the EPSS score of < 1 % signals a very low probability of active exploitation at the time of this analysis. The bug is not listed in the CISA KEV catalog. The inferred attack vector is the delivery of a crafted Bluetooth L2CAP packet that provides a conflicting dcid, which does not require elevated privileges or special physical proximity beyond normal Bluetooth communication. The exploit would simply crash the kernel, potentially requiring a reboot to recover.
OpenCVE Enrichment
Ubuntu USN