CVE-2026-68339

Bluetooth: btusb: validate Realtek vendor event length

Published Aug 10, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability resides in the Linux Bluetooth USB driver (btusb) when it processes vendor events from Realtek adapters. The btusb_recv_event_realtek function reads the event code at data[0] and the vendor‑specific subevent code at data[2] prior to determining whether the event should be treated as a coredump. Because the implementation assumes that the packet contains a third byte, an event packet that is shorter than expected can cause the function to read beyond the packet boundary. This out‑of‑bounds read may lead the driver to mistakenly classify a short, normal event as a fatal coredump, which can trigger a kernel crash and deny service to the affected host.

Affected Systems

Affected systems include any Linux kernel that has not yet integrated the validation patch for btusb vendor event length. The flaw impacts the btusb driver and applies to Realtek USB Bluetooth adapters that send vendor‑specific event packets. Distributions that ship unpatched kernels with active Bluetooth support—and particularly those that allow Realtek adapters to be connected—are vulnerable regardless of the system architecture.

Risk and Exploitability

The CVSS score is 6.5, the EPSS score is < 1%, and it is not listed in the CISA KEV catalog, indicating no known widespread exploitation. Based on the description, it is inferred that an attacker would need to transmit a crafted Bluetooth vendor event packet to a Realtek USB adapter, which could be achieved from a nearby malicious device or through a compromised local adapter. Because the exploit requires direct interaction with the Bluetooth interface and no public proof of concept is available, the overall risk may be considered moderate, but the potential impact of a kernel crash remains high.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the kernel to a version that includes the btusb vendor event length validation patch as referenced in the commit series.
  • If an immediate kernel upgrade is not possible, disable or isolate the Bluetooth interface to prevent external vendor events from reaching the btusb driver.
  • Monitor kernel logs for unexpected coredump events related to Bluetooth and apply additional system hardening such as disabling unused Bluetooth services.
  • Apply host‑based firewall rules or local security controls to limit traffic to Bluetooth interfaces, reducing the chance of a crafted packet reaching the vulnerable driver.

Generated by OpenCVE AI on August 12, 2026 at 18:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4745-1 linux-6.12 security update
Ubuntu USN Ubuntu USN USN-8887-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8888-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8889-1 Linux kernel (OEM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8887-2 Linux kernel (AWS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8888-2 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8887-3 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8917-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8918-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9003-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-9024-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9025-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9026-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9040-1 Linux kernel (Low Latency NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-9043-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-9066-1 Linux kernel (HWE) vulnerabilities
Ubuntu USN Ubuntu USN USN-9091-1 Linux kernel (NVIDIA Tegra) vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-125
References
Metrics threat_severity

None

cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate

Type Values Removed Values Added
Weaknesses CWE-20
Type Values Removed Values Added
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.
Title Bluetooth: btusb: validate Realtek vendor event length
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Aug 17, 2026, 5:03 AM
Reserved
Jul 30, 2026, 9:28 AM
Status
Received
Published
Aug 10, 2026, 1:20 PM
Modified
Aug 17, 2026, 6:17 AM
Severity
Moderate
Public date
Aug 10, 2026, 12:03 PM