Impact
In the Linux kernel’s Bluetooth HID Protocol driver, a received numbered report is compared against a value in the socket buffer without first confirming that a payload byte actually exists. This oversight can lead to an out‑of‑bounds read or use of an uninitialized value, potentially causing the kernel to crash or halt the HID subsystem. No code execution or privilege escalation is currently possible, but a kernel panic would disrupt services that rely on the Bluetooth HID interface.
Affected Systems
Any Linux kernel that has not incorporated the HIDP payload validation fix is vulnerable. This includes mainstream distribution kernel releases as well as embedded Linux devices that enable Bluetooth HID support. Devices that expose the Bluetooth HID interface and accept peer‑controlled input are affected.
Risk and Exploitability
The CVSS score of 7.1 indicates moderate‑to‑high severity, while the EPSS score of less than 1% suggests a low likelihood of exploitation in the wild. The vulnerability is not listed in the CISA KEV catalog. Attackers would need to establish an active Bluetooth HID connection and send specially crafted reports; successful exploitation would primarily produce a kernel error or denial of the HID service rather than data compromise or system takeover.
OpenCVE Enrichment
Debian DSA