CVE-2026-97977: Linux kernel · Bluetooth: btusb: Fix UAF of btusb_data by rx_work
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in fc654a72a8d979db15e2773a481e931abaf5a9e8 : patch Linux kernel soon.
Data as of 26 Oct 2026, 14:05 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in fc654a72a8d979db15e2773a481e931abaf5a9e8, fa391adb9c755515a89993634745e9079e5ef37c, 5242050195a711e9cd6a9935f689ab6656b94a91 +3
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel. Users should update to a kernel version that includes the commit fixes identified by the provided hashes. No additional mitigation steps are indicated or necessary beyond applying the official patch.
Description
A use-after-free (UAF) vulnerability was identified and fixed in the Linux kernel's Bluetooth USB driver (btusb). The issue arises because btusb_close() and btusb_flush() cancel a delayed work item asynchronously, allowing the work to continue running on another CPU after the data structure has been freed. This leads to dereferencing freed memory in btusb_rx_work(). The fix involves using a synchronous cancel function and adjusting the order of operations to prevent race conditions.
References
- git.kernel.org/stable/c/fc654a72a8d979db15e2773a481e931abaf5a9e8 (opens in a new tab)
- git.kernel.org/stable/c/5242050195a711e9cd6a9935f689ab6656b94a91 (opens in a new tab)
- git.kernel.org/stable/c/472d005622525b7be155cac99dde2252b0163bd1 (opens in a new tab)
- git.kernel.org/stable/c/93b59937bda3fffc6386c79f5544a39bc680c8e8 (opens in a new tab)
- git.kernel.org/stable/c/fa391adb9c755515a89993634745e9079e5ef37c (opens in a new tab)
- git.kernel.org/stable/c/1c12c3117639e78940959d956519c758c57d0849 (opens in a new tab)