CVE-2026-98906: Linux kernel · net: lan966x: restore RX state on reload failure
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in b5a6462f4646687c922931133a2478da94addc87 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 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 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in b5a6462f4646687c922931133a2478da94addc87, aa97f11a76e545ed73cc455bcdd1ece4b480b507, 3883898ddc26308497dbba8068951ab5eddbd111
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 Linux kernel to b5a6462f4646687c922931133a2478da94addc87, aa97f11a76e545ed73cc455bcdd1ece4b480b507 or 3883898ddc26308497dbba8068951ab5eddbd111.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
This vulnerability has been fixed in the Linux kernel commits identified by hashes b5a6462f4646687c922931133a2478da94addc87, aa97f11a76e545ed73cc455bcdd1ece4b480b507, and 3883898ddc26308497dbba8068951ab5eddbd111. Users should update to a Linux kernel version that includes these fixes. No additional mitigation is required.
Description
A vulnerability in the Linux kernel's lan966x network driver involves improper restoration of RX state after a reload failure. Specifically, certain fields related to RX page geometry and page pool registration are not restored correctly if resource reallocation fails, potentially causing inconsistencies in frame size handling in the XDP path. This issue has been fixed in specific Linux kernel commits.