A failure in the Bluetooth HCI UART initialization path in the Linux kernel can cause the SRCU structure allocated by hci_alloc_dev() not to be cleaned up when bt_host_release() is invoked before hci_register_dev() succeeds. The missing cleanup leaves per‑CPU memory allocated, which steadily accumulates as the device is repeatedly attempted to be provisioned and fails. This improper release of resources (CWE‑687) can result in kernel memory exhaustion, ultimately bringing the system to a denial‑of‑service state.

All Linux kernel builds that include the Bluetooth subsystem prior to the fix commit are affected. The vulnerability exists in every distribution that ships the unsupported kernel version; any vendor using a kernel older than the applied patch is at risk.

The CVSS score is not publicly listed, and EPSS is not available, but the lack of this vulnerability in the CISA KEV catalog and the absence of a known remote exploitation path suggests a moderate risk. An attacker would need to force repeated HCI device initialization failures, which typically requires local or privileged access; the attack vector is therefore inferred to be local or privileged rather than remote. The primary impact is availability‑downtime due to memory exhaustion rather than confidentiality or integrity compromise.