CVE-2026-98890: Linux kernel · wifi: libertas: reject short monitor TX frames
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d865dd6de8295f2bfaa83f0f5d49d2bef1543065 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:00 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in d865dd6de8295f2bfaa83f0f5d49d2bef1543065, cdcfd662c67833d89ee3d912efde2eb67c8a7326, b657cc98d7936c5d9ed7e0e1944ad0e1f36375bb +4
Exploitation evidence
Disclosed: evidence found.
CVE published 23 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. Users should update to a kernel version that includes the commits identified as fixes (e.g., those with hashes d865dd6de8295f2bfaa83f0f5d49d2bef1543065 and others). No additional mitigation actions are required beyond applying the official patch.
Description
A vulnerability in the Linux kernel's libertas wifi driver allows short monitor TX frames to be processed without adequate length checks, potentially causing out-of-bounds reads. The issue arises because the function handling monitor mode frames does not verify that the frame length is sufficient before accessing the destination address field. This flaw has been fixed by requiring enough bytes for the radiotap TX header and destination address before processing the frame.
References
- git.kernel.org/stable/c/68c92c991ddb75dfd3fd62a94a1d4d2dde44dc3c (opens in a new tab)
- git.kernel.org/stable/c/d865dd6de8295f2bfaa83f0f5d49d2bef1543065 (opens in a new tab)
- git.kernel.org/stable/c/6576baa3fdbaa91fa75e4ba27095f4b8a27349a8 (opens in a new tab)
- git.kernel.org/stable/c/b657cc98d7936c5d9ed7e0e1944ad0e1f36375bb (opens in a new tab)
- git.kernel.org/stable/c/443fac3de65c76544b450b9f9903be8989150d55 (opens in a new tab)
- git.kernel.org/stable/c/cdcfd662c67833d89ee3d912efde2eb67c8a7326 (opens in a new tab)
- git.kernel.org/stable/c/13ff543e0b2c713aedeaadadde686686e949dc78 (opens in a new tab)