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.

No CVSS v4.0

No CVSS v3.1

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

No EPSS score available.

Key SSVC decision points have not yet been added.

Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).

Vendor Product Default status Versions
Linux Linux unaffected
Version Status Constraints
044014ce85a17c0b7fab8e5df0925792010c29b2 affected < 8de58bfa26e028f99271dde5a92107cd07f5e063
044014ce85a17c0b7fab8e5df0925792010c29b2 affected < 400267bab0f4076088e163e58cad2bb41c3cf5e7
044014ce85a17c0b7fab8e5df0925792010c29b2 affected < 8881daaafadbe7fb2b7341d16a3949114409c90c
044014ce85a17c0b7fab8e5df0925792010c29b2 affected < 24b0758193d70da47ef8b979153d2a181dbdf34e
044014ce85a17c0b7fab8e5df0925792010c29b2 affected < df541cd485ff80a5ddc579d99687bc7506df9851
Linux Linux affected
Version Status Constraints
6.6 affected —
0 unaffected < 6.6
6.6.148 unaffected ≤ 6.6.*
6.12.101 unaffected ≤ 6.12.*
6.18.42 unaffected ≤ 6.18.*
7.1.6 unaffected ≤ 7.1.*
7.2-rc5 unaffected ≤ *

No data.

No data.

OpenCVE Enrichment is a feature of OpenCVE that uses AI to automatically link vendors and products to CVEs. Learn more on GitHub.

No data.

Project Subscriptions

Vendors Products
Linux Subscribe
Linux Kernel Subscribe
Advisories

No advisories yet.

Fixes

Solution

No solution given by the vendor.

Workaround

No workaround given by the vendor.

References
Link Providers
https://git.kernel.org/stable/c/24b0758193d70da47ef8b979153d2a181dbdf34e cve-icon
https://git.kernel.org/stable/c/400267bab0f4076088e163e58cad2bb41c3cf5e7 cve-icon
https://git.kernel.org/stable/c/8881daaafadbe7fb2b7341d16a3949114409c90c cve-icon
https://git.kernel.org/stable/c/8de58bfa26e028f99271dde5a92107cd07f5e063 cve-icon
https://git.kernel.org/stable/c/df541cd485ff80a5ddc579d99687bc7506df9851 cve-icon
History

Mon, 10 Aug 2026 17:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-20

Mon, 10 Aug 2026 12:30:00 +0000

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

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-10T12:03:15.551Z

Reserved: 2026-07-30T09:28:09.384Z

Link: CVE-2026-68339

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-10T16:45:03Z

Weaknesses