btusb_recv_event_realtek
drivers/bluetooth/btusb.c
Last patched
Overview
btusb_recv_event_realtek in torvalds/linux was changed by 1 published CVE fixes in 2026, in 10 distinct patches that added or removed 4 lines in total.
torvalds/linux has 19,281 CVEs with a located fix in total, so 0% of them touched this function.
CVEs that patched it
Every published CVE whose fix changed btusb_recv_event_realtek, newest first, with the lines each fix touched.
CVE-2026-68339 · lines 2719–2721 · +3 −1
UnscoredEPSS 0.2%2026-08-10
Get an alert when the next CVE fix lands in torvalds/linux, with the patched functions.
Monitor linux CVEsOther functions in these files
Functions in the same file that CVE fixes also changed.
- 1btusb_probedrivers/bluetooth/btusb.c5 CVEs · 45 patches2024 to 2026
- 2btusb_disconnectdrivers/bluetooth/btusb.c2 CVEs · 15 patches2025 to 2026
- 3btusb_mtk_claim_iso_intfdrivers/bluetooth/btusb.c2 CVEs · 7 patches2024 to 2025
- 4btusb_flushdrivers/bluetooth/btusb.c1 CVEs · 9 patches2026
- 5btusb_closedrivers/bluetooth/btusb.c1 CVEs · 9 patches2026
- 6btusb_workdrivers/bluetooth/btusb.c1 CVEs · 9 patches2026
- 7btusb_mtk_hci_wmt_syncdrivers/bluetooth/btusb.c1 CVEs · 7 patches2024
- 8usb_driver_claim_interfacedrivers/bluetooth/btusb.c1 CVEs · 4 patches2025
Other hotspots in the repository
Functions in torvalds/linux changed by the most CVE fixes.
Frequently asked questions
Common questions about CVE fixes to btusb_recv_event_realtek.
- How many CVEs have patched btusb_recv_event_realtek?
- 1 published CVEs changed btusb_recv_event_realtek in torvalds/linux, in 10 distinct patches totalling 4 changed lines, between 2026 and 2026.
- What is the latest CVE that changed btusb_recv_event_realtek?
- CVE-2026-68339 (Bluetooth: btusb: validate Realtek vendor event length), published 2026-08-10, changed lines 2719 to 2721 of drivers/bluetooth/btusb.c.
- How does btusb_recv_event_realtek compare to the rest of torvalds/linux?
- torvalds/linux has 19,281 CVEs with a located fix in total; 1 of them changed btusb_recv_event_realtek.
- What do the line numbers refer to?
- Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.
References
- drivers/bluetooth/btusb.c on GitHub (opens in a new tab)
- All patched functions in torvalds/linux
- Patched functions directory
Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.
Track torvalds/linux CVEs
Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.