CVE-2026-68339
Last modified
CVE-2026-68339 is a vulnerability of currently unknown severity. 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.
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.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 044014ce85a17c0b7fab8e5df0925792010c29b2, < 8de58bfa26e028f99271dde5a92107cd07f5e063; >= 044014ce85a17c0b7fab8e5df0925792010c29b2, < 400267bab0f4076088e163e58cad2bb41c3cf5e7; >= 044014ce85a17c0b7fab8e5df0925792010c29b2, < 8881daaafadbe7fb2b7341d16a3949114409c90c; >= 044014ce85a17c0b7fab8e5df0925792010c29b2, < 24b0758193d70da47ef8b979153d2a181dbdf34e; >= 044014ce85a17c0b7fab8e5df0925792010c29b2, < df541cd485ff80a5ddc579d99687bc7506df9851 |
| Linux | Linux | 6.6 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-68339?
How severe is CVE-2026-68339?
How do I fix CVE-2026-68339?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-68333In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68334In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68335In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68336In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68337In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68338In the Linux kernel, the following vulnerability has been re…
- CVE-2026-6834The a+HRD developed by aEnrich has a Missing Authorization v…7.1
- CVE-2026-68340In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68341In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68342In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68343In the Linux kernel, the following vulnerability has been re…
- CVE-2026-68344In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-68339?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST