Answer in brief
CVE-2026-68339 records a Unknown severity vulnerability in Bluetooth: btusb: validate Realtek vendor event length. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=044014ce85a17c0b7fab8e5df0925792010c29b2 <8de58bfa26e028f99271dde5a92107cd07f5e063 || >=044014ce85a17c0b7fab8e5df0925792010c29b2 <400267bab0f4076088e163e58cad2bb41c3cf5e7 || >=044014ce85a17c0b7fab8e5df0925792010c29b2 <8881daaafadbe7fb2b7341d16a3949114409c90c || >=044014ce85a17c0b7fab8e5df0925792010c29b2 <24b0758193d70da47ef8b979153d2a181dbdf34e || >=044014ce85a17c0b7fab8e5df0925792010c29b2 <df541cd485ff80a5ddc579d99687bc7506df9851 | 8de58bfa26e028f99271dde5a92107cd07f5e063, 400267bab0f4076088e163e58cad2bb41c3cf5e7, 8881daaafadbe7fb2b7341d16a3949114409c90c, 24b0758193d70da47ef8b979153d2a181dbdf34e, df541cd485ff80a5ddc579d99687bc7506df9851 |
| Linux/Linuxgeneric | 6.6 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68339 records a Unknown severity vulnerability in Bluetooth: btusb: validate Realtek vendor event length. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=044014ce85a17c0b7fab8e5df0925792010c29b2 <8de58bfa26e028f99271dde5a92107cd07f5e063 || >=044014ce85a17c0b7fab8e5df0925792010c29b2 <400267bab0f4076088e163e58cad2bb41c3cf5e7 || >=044014ce85a17c0b7fab8e5df0925792010c29b2 <8881daaafadbe7fb2b7341d16a3949114409c90c || >=044014ce85a17c0b7fab8e5df0925792010c29b2 <24b0758193d70da47ef8b979153d2a181dbdf34e || >=044014ce85a17c0b7fab8e5df0925792010c29b2 <df541cd485ff80a5ddc579d99687bc7506df9851 | 8de58bfa26e028f99271dde5a92107cd07f5e063, 400267bab0f4076088e163e58cad2bb41c3cf5e7, 8881daaafadbe7fb2b7341d16a3949114409c90c, 24b0758193d70da47ef8b979153d2a181dbdf34e, df541cd485ff80a5ddc579d99687bc7506df9851 |
| Linux/Linuxgeneric | 6.6 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.