All reports
Medium

kernel: Bluetooth: btusb: validate Realtek vendor event length

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-68339

Probability of exploitation in the next 30 days: 0.21%

FIRST EPSS · 2026-11-20

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btusb: validate Realtek vendor event length btusb_recv_event_realtek() reads the event code at data[0] and the Realtek subevent code at data[2] before deciding whether to consume a vendor event as a coredump. For example, the two-byte event ff 00 contains a complete vendor-event header declaring zero parameters. The old classifier still reads a nonexistent third byte and can misclassify the event as a coredump if the adjacent byte is 0x34. Require the HCI event header and first parameter to be present before inspecting the Realtek subevent code. Short events continue through the normal HCI receive path, which owns their protocol validation.

A flaw was found in the Linux kernel's Bluetooth subsystem (btusb driver). An attacker could craft a two-byte vendor event that, due to improper validation of the Realtek vendor event length in the btusb_recv_event_realtek() function, could lead to the system attempting to read a non-existent third byte. This misclassification of the event as a coredump could result in a denial of service (DoS).