CVE-2026-98194: Linux kernel · wifi: libertas_tf: fix UAF in lbtf_free_adapter()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f6c3fa0d17ca0c9e6033bb45f52e33b27a9a40e6 : patch Linux kernel soon.
Data as of 26 Oct 2026, 13:47 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 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f6c3fa0d17ca0c9e6033bb45f52e33b27a9a40e6, e82536aad653e27c8ca7a8e0f6f816bc3f853ec3, bbb9a0ab96d44a64529aafc7a16de460a1712f6a +5
Exploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 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 source code. Users should update to a fixed kernel version that includes the patch identified by the listed commit hashes. No additional mitigation is required once the patch is applied.
Description
A use-after-free (UAF) vulnerability was identified and fixed in the Linux kernel's libertas_tf wifi driver in the function lbtf_free_adapter(). The issue arises because the command buffers are freed before ensuring that any in-flight timer callback accessing those buffers has completed, leading to a potential dereference of freed memory. The fix involves changing the order of operations to delete the timer synchronously before freeing the command buffers.
References
- git.kernel.org/stable/c/3fb3663260ec396f86b733aab9f81fac6669d2fa (opens in a new tab)
- git.kernel.org/stable/c/f6c3fa0d17ca0c9e6033bb45f52e33b27a9a40e6 (opens in a new tab)
- git.kernel.org/stable/c/b4745d6063758c681d33affca9733bbd356b6ea1 (opens in a new tab)
- git.kernel.org/stable/c/41b1a4d545ec348b7d5324b6d4f4c6a3e0326d46 (opens in a new tab)
- git.kernel.org/stable/c/2b99bfc5a127ce8cd6a887d82815fc2e712f365b (opens in a new tab)
- git.kernel.org/stable/c/e82536aad653e27c8ca7a8e0f6f816bc3f853ec3 (opens in a new tab)
- git.kernel.org/stable/c/04c837d413dc11a91e0275b08b9e35a6c111175e (opens in a new tab)
- git.kernel.org/stable/c/bbb9a0ab96d44a64529aafc7a16de460a1712f6a (opens in a new tab)