CVE-2025-68298: Bluetooth: btusb: mediatek: Avoid btusb_mtk_claim_iso_intf() NULL deref

Severity: unknown
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2025-12-16 · updated 2026-10-14

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btusb: mediatek: Avoid btusb_mtk_claim_iso_intf() NULL deref In btusb_mtk_setup(), we set `btmtk_data->isopkt_intf` to: usb_ifnum_to_if(data->udev, MTK_ISO_IFNUM) That function can return NULL in some cases. Even when it returns NULL, though, we still go on to call btusb_mtk_claim_iso_intf(). As of commit e9087e828827 ("Bluetooth: btusb: mediatek: Add locks for usb_driver_claim_interface()"), calling btusb_mtk_claim_iso_intf() when `btmtk_data->isopkt_intf` is NULL will cause a crash because we'll end up passing a bad pointer to device_lock(). Prior to that commit we'd pass the NULL pointer directly to usb_driver_claim_interface() which would detect it and return an error, which was handled. Resolve the crash in btusb_mtk_claim_iso_intf() by adding a NULL check at the start of the function. This makes the code handle a NULL `btmtk_data->isopkt_intf` the same way it did before the problematic commit (just with a slight change to the error message printed).

Affected products

Linux kernel: from 6.12.13 before 6.12.61; from 6.13.2 before 6.14; 6.14 — fixed in 6.12.61, 6.14, 6.18

How to fix

Upgrade to a fixed version: Linux kernel 6.12.61, 6.14, 6.18. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2025-68298 or the next vulnerability affects your stack