CVE-2026-68339

medium

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.

References

https://git.kernel.org/stable/c/df541cd485ff80a5ddc579d99687bc7506df9851

https://git.kernel.org/stable/c/8de58bfa26e028f99271dde5a92107cd07f5e063

https://git.kernel.org/stable/c/8881daaafadbe7fb2b7341d16a3949114409c90c

https://git.kernel.org/stable/c/400267bab0f4076088e163e58cad2bb41c3cf5e7

https://git.kernel.org/stable/c/24b0758193d70da47ef8b979153d2a181dbdf34e

Details

Source: Mitre, NVD

Published: 2026-08-10

Updated: 2026-08-10

Risk Information

CVSS v2

Base Score: 4.6

Vector: CVSS2#AV:L/AC:L/Au:S/C:N/I:N/A:C

Severity: Medium

CVSS v3

Base Score: 5.5

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Severity: Medium

EPSS

EPSS: 0.00209