Answer in brief
CVE-2025-21827 records a Unknown severity vulnerability in Bluetooth: btusb: mediatek: Add locks for usb_driver_claim_interface(). 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 | >=ceac1cb0259de682d78f5c784ef8e0b13022e9d9 <930e1790b99e5839e1af69d2f7fd808f1fba2df9 || >=ceac1cb0259de682d78f5c784ef8e0b13022e9d9 <4194766ec8756f4f654d595ae49962acbac49490 || >=ceac1cb0259de682d78f5c784ef8e0b13022e9d9 <e9087e828827e5a5c85e124ce77503f2b81c3491 | 930e1790b99e5839e1af69d2f7fd808f1fba2df9, 4194766ec8756f4f654d595ae49962acbac49490, e9087e828827e5a5c85e124ce77503f2b81c3491 |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Mar 6, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btusb: mediatek: Add locks for usb_driver_claim_interface() The documentation for usb_driver_claim_interface() says that "the device lock" is needed when the function is called from places other than probe(). This appears to be the lock for the USB interface device. The Mediatek btusb code gets called via this path: Workqueue: hci0 hci_power_on [bluetooth] Call trace: usb_driver_claim_interface btusb_mtk_claim_iso_intf btusb_mtk_setup hci_dev_open_sync hci_power_on process_scheduled_works worker_thread kthread With the above call trace the device lock hasn't been claimed. Claim it. Without this fix, we'd sometimes see the error "Failed to claim iso interface". Sometimes we'd even see worse errors, like a NULL pointer dereference (where `intf->dev.driver` was NULL) with a trace like: Call trace: usb_suspend_both usb_runtime_suspend __rpm_callback rpm_suspend pm_runtime_work process_scheduled_works Both errors appear to be fixed with the proper locking.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-21827 records a Unknown severity vulnerability in Bluetooth: btusb: mediatek: Add locks for usb_driver_claim_interface(). 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 | >=ceac1cb0259de682d78f5c784ef8e0b13022e9d9 <930e1790b99e5839e1af69d2f7fd808f1fba2df9 || >=ceac1cb0259de682d78f5c784ef8e0b13022e9d9 <4194766ec8756f4f654d595ae49962acbac49490 || >=ceac1cb0259de682d78f5c784ef8e0b13022e9d9 <e9087e828827e5a5c85e124ce77503f2b81c3491 | 930e1790b99e5839e1af69d2f7fd808f1fba2df9, 4194766ec8756f4f654d595ae49962acbac49490, e9087e828827e5a5c85e124ce77503f2b81c3491 |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Mar 6, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btusb: mediatek: Add locks for usb_driver_claim_interface() The documentation for usb_driver_claim_interface() says that "the device lock" is needed when the function is called from places other than probe(). This appears to be the lock for the USB interface device. The Mediatek btusb code gets called via this path: Workqueue: hci0 hci_power_on [bluetooth] Call trace: usb_driver_claim_interface btusb_mtk_claim_iso_intf btusb_mtk_setup hci_dev_open_sync hci_power_on process_scheduled_works worker_thread kthread With the above call trace the device lock hasn't been claimed. Claim it. Without this fix, we'd sometimes see the error "Failed to claim iso interface". Sometimes we'd even see worse errors, like a NULL pointer dereference (where `intf->dev.driver` was NULL) with a trace like: Call trace: usb_suspend_both usb_runtime_suspend __rpm_callback rpm_suspend pm_runtime_work process_scheduled_works Both errors appear to be fixed with the proper locking.
Quoted source text, attributed separately from HOL analysis.