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-2026-97977Bluetooth: btusb: Fix UAF of btusb_data by rx_work

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btusb: Fix UAF of btusb_data by rx_work btusb_close() and btusb_flush() cancel data->rx_work with the asynchronous cancel_delayed_work(), so if btusb_rx_work() is already running on another CPU it keeps running after the cancel returns. btusb_disconnect() calls hci_unregister_dev(), which invokes btusb_close(), and then frees the btusb_data. A still running btusb_rx_work() then dereferences the freed data: while ((skb = skb_dequeue(&data->acl_q))) data->recv_acl(data->hdev, skb); Use cancel_delayed_work_sync() instead. In btusb_close() the cancel also has to happen after btusb_stop_traffic(), otherwise an URB completion racing with the cancel can requeue the work right after it has been waited for.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 24 days 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: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (13 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 800fe5ec302e1ebbf5e3f891f886deecd49c7132 – < fc654a72a8d979db15e2773a481e931abaf5a9e8
    • affected 800fe5ec302e1ebbf5e3f891f886deecd49c7132 – < 5242050195a711e9cd6a9935f689ab6656b94a91
    • affected 800fe5ec302e1ebbf5e3f891f886deecd49c7132 – < 472d005622525b7be155cac99dde2252b0163bd1
    • affected 800fe5ec302e1ebbf5e3f891f886deecd49c7132 – < 93b59937bda3fffc6386c79f5544a39bc680c8e8
    • affected 800fe5ec302e1ebbf5e3f891f886deecd49c7132 – < fa391adb9c755515a89993634745e9079e5ef37c
    • affected 800fe5ec302e1ebbf5e3f891f886deecd49c7132 – < 1c12c3117639e78940959d956519c758c57d0849
  • Linux · Linux

    • affected 5.17
    • unaffected < 5.17
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .