CVE-2026-98830: Linux kernel · wifi: wfx: validate MIB read length before copying to caller
Source GCVE Database
Not known to be exploited · fixed in ce67ebe9d8629776ce38e6995ae72fb903c828db : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:16 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in ce67ebe9d8629776ce38e6995ae72fb903c828db, 02886c18a340da59df57365f29009e1258bfe333, 819d4c1323e2a9b7329021d5367aa01add22b5dc +2
Exploitation evidence
Disclosed: evidence found.
CVE published 18 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 has been implemented that validates the reply length before copying data, preventing buffer over-read. Users should apply the official Linux kernel update that includes this patch to remediate the vulnerability.
Description
A vulnerability in the Linux kernel's wifi wfx driver was resolved by adding validation of the MIB read length before copying data to the caller. The function wfx_hif_read_mib() previously copied reply->length bytes from the firmware response into a caller buffer without verifying that reply->length did not exceed the buffer size val_len. This could lead to a buffer over-read and potential memory corruption. The fix replaces a non-functional -ENOMEM check with an active validation to ensure reply->length fits within val_len before memcpy.
References
- nvd.nist.gov/vuln/detail/CVE-2026-98830 (opens in a new tab)
- git.kernel.org/stable/c/02886c18a340da59df57365f29009e1258bfe333 (opens in a new tab)
- git.kernel.org/stable/c/71d140099165de03128c00dd129f1eab21c6a3c4 (opens in a new tab)
- git.kernel.org/stable/c/7acb36fd60a3e7b858f12e69a919c3609b281408 (opens in a new tab)
- git.kernel.org/stable/c/ce67ebe9d8629776ce38e6995ae72fb903c828db (opens in a new tab)
- git.kernel.org/stable/c/819d4c1323e2a9b7329021d5367aa01add22b5dc (opens in a new tab)