CVE-2025-68298
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-16

Last updated on: 2025-12-18

Assigner: kernel.org

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).
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-16
Last Modified
2025-12-18
Generated
2026-05-07
AI Q&A
2025-12-16
EPSS Evaluated
2026-05-05
NVD
CVE-2025-68298
EUVD
EUVD-2025-203782
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a NULL pointer dereference in the Linux kernel's Bluetooth Mediatek USB driver (btusb). Specifically, in the function btusb_mtk_setup(), a pointer (btmtk_data->isopkt_intf) can be set to NULL by the function usb_ifnum_to_if(). Despite this, the code proceeds to call btusb_mtk_claim_iso_intf() without checking if the pointer is NULL. After a certain commit, calling btusb_mtk_claim_iso_intf() with a NULL pointer causes a crash due to passing a bad pointer to device_lock(). The vulnerability is fixed by adding a NULL check at the start of btusb_mtk_claim_iso_intf(), preventing the crash.


What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, update your Linux kernel to a version that includes the fix for the btusb Mediatek driver, specifically the commit e9087e828827 or later. This update adds a NULL check in btusb_mtk_claim_iso_intf() to prevent crashes caused by NULL pointer dereferences. Until the update is applied, avoid using affected Bluetooth Mediatek USB devices if possible.


How can this vulnerability impact me? :

This vulnerability can cause the Linux kernel to crash when the Bluetooth Mediatek USB driver encounters a NULL pointer dereference. This crash can lead to system instability or denial of service, as the kernel may panic or become unresponsive due to the invalid pointer access.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart