CVE-2026-68339
Bluetooth: btusb: validate Realtek vendor event length
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.
INFO
Published Date :
Aug. 10, 2026, 1:20 p.m.
Last Modified :
Aug. 10, 2026, 1:20 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-68339
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Apply kernel patches for the btusb vulnerability.
- Update the Linux kernel to a fixed version.
- Ensure HCI event header and parameters are validated.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-68339.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-68339 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-68339
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-68339 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-68339 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Aug. 10, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '044014ce85a17c0b7fab8e5df0925792010c29b2', 'lessThan': '8de58bfa26e028f99271dde5a92107cd07f5e063', 'versionType': 'git'}, {'status': 'affected', 'version': '044014ce85a17c0b7fab8e5df0925792010c29b2', 'lessThan': '400267bab0f4076088e163e58cad2bb41c3cf5e7', 'versionType': 'git'}, {'status': 'affected', 'version': '044014ce85a17c0b7fab8e5df0925792010c29b2', 'lessThan': '8881daaafadbe7fb2b7341d16a3949114409c90c', 'versionType': 'git'}, {'status': 'affected', 'version': '044014ce85a17c0b7fab8e5df0925792010c29b2', 'lessThan': '24b0758193d70da47ef8b979153d2a181dbdf34e', 'versionType': 'git'}, {'status': 'affected', 'version': '044014ce85a17c0b7fab8e5df0925792010c29b2', 'lessThan': 'df541cd485ff80a5ddc579d99687bc7506df9851', 'versionType': 'git'}], 'programFiles': ['drivers/bluetooth/btusb.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '6.6'}, {'status': 'unaffected', 'version': '0', 'lessThan': '6.6', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.6.148', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.101', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.42', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.6', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc5', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/bluetooth/btusb.c'], 'defaultStatus': 'affected'}] 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. Added Reference https://git.kernel.org/stable/c/24b0758193d70da47ef8b979153d2a181dbdf34e Added Reference https://git.kernel.org/stable/c/400267bab0f4076088e163e58cad2bb41c3cf5e7 Added Reference https://git.kernel.org/stable/c/8881daaafadbe7fb2b7341d16a3949114409c90c Added Reference https://git.kernel.org/stable/c/8de58bfa26e028f99271dde5a92107cd07f5e063 Added Reference https://git.kernel.org/stable/c/df541cd485ff80a5ddc579d99687bc7506df9851