Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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).

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.20% · top 91% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 930e1790b99e5839e1af69d2f7fd808f1fba2df9 – < 2fa09fe98ca3b114d66285f65f7e108fea131815
    • affected e9087e828827e5a5c85e124ce77503f2b81c3491 – < c3b990e0b23068da65f0004cd38ee31f43f36460
    • affected e9087e828827e5a5c85e124ce77503f2b81c3491 – < c884a0b27b4586e607431d86a1aa0bb4fb39169c
    • affected 4194766ec8756f4f654d595ae49962acbac49490
    • affected 6.12.13 – < 6.12.61
    • affected 6.13.2 – < 6.14
  • Linux · Linux

    • affected 6.14
    • unaffected < 6.14
    • unaffected 6.12.61 – ≤ 6.12.*
    • unaffected 6.17.11 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-68298 badge
[![CVE-2025-68298](https://cveledger.app/badge/CVE-2025-68298.svg)](https://cveledger.app/cve/CVE-2025-68298)

Record last updated .