{"id":"CVE-2025-68298","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: btusb: mediatek: Avoid btusb_mtk_claim_iso_intf() NULL deref\n\nIn btusb_mtk_setup(), we set `btmtk_data->isopkt_intf` to:\n  usb_ifnum_to_if(data->udev, MTK_IS…","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: btusb: mediatek: Avoid btusb_mtk_claim_iso_intf() NULL deref\n\nIn btusb_mtk_setup(), we set `btmtk_data->isopkt_intf` to:\n  usb_ifnum_to_if(data->udev, MTK_IS…","severity":"none","published":"2025-12-16","updated":"2026-10-14","sourceUpdated":"2026-10-14T16:10:00.250","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2025-68298","references":[{"url":"https://git.kernel.org/stable/c/2fa09fe98ca3b114d66285f65f7e108fea131815","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/c3b990e0b23068da65f0004cd38ee31f43f36460","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/c884a0b27b4586e607431d86a1aa0bb4fb39169c","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}],"tags":["nvd"],"epss":0.00185,"epssPercentile":0.07543,"ingestedAt":"2026-10-14T16:40:32.051Z","slug":"CVE-2025-68298","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: btusb: mediatek: Avoid btusb_mtk_claim_iso_intf() NULL deref\n\nIn btusb_mtk_setup(), we set `btmtk_data->isopkt_intf` to:\n  usb_ifnum_to_if(data->udev, MTK_ISO_IFNUM)\n\nThat function can return NULL in some cases. Even when it returns\nNULL, though, we still go on to call btusb_mtk_claim_iso_intf().\n\nAs of commit e9087e828827 (\"Bluetooth: btusb: mediatek: Add locks for\nusb_driver_claim_interface()\"), calling btusb_mtk_claim_iso_intf()\nwhen `btmtk_data->isopkt_intf` is NULL will cause a crash because\nwe'll end up passing a bad pointer to device_lock(). Prior to that\ncommit we'd pass the NULL pointer directly to\nusb_driver_claim_interface() which would detect it and return an\nerror, which was handled.\n\nResolve the crash in btusb_mtk_claim_iso_intf() by adding a NULL check\nat the start of the function. This makes the code handle a NULL\n`btmtk_data->isopkt_intf` the same way it did before the problematic\ncommit (just with a slight change to the error message printed).\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}