VulnerabilityPublished 23 Oct 2026

CVE-2026-98906: Linux kernel · net: lan966x: restore RX state on reload failure

Source GCVE Database

Authoritative record:CVE-2026-98906· Medium

Not known to be exploited · fixed in b5a6462f4646687c922931133a2478da94addc87 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity

Medium

Rated by Threat Radar · 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-2fw9-6rfh-9q85

What to do

Upgrade Linux kernel to b5a6462f4646687c922931133a2478da94addc87, aa97f11a76e545ed73cc455bcdd1ece4b480b507 or 3883898ddc26308497dbba8068951ab5eddbd111.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 2ea1cbac267e2a39546982612fc00084b6d93e40, < b5a6462f4646687c922931133a2478da94addc87	Fixed in b5a6462f4646687c922931133a2478da94addc87
LinuxLinux	Affected ≥ 2ea1cbac267e2a39546982612fc00084b6d93e40, < aa97f11a76e545ed73cc455bcdd1ece4b480b507	Fixed in aa97f11a76e545ed73cc455bcdd1ece4b480b507
LinuxLinux	Affected ≥ 2ea1cbac267e2a39546982612fc00084b6d93e40, < 3883898ddc26308497dbba8068951ab5eddbd111	Fixed in 3883898ddc26308497dbba8068951ab5eddbd111
LinuxLinux	Affected =5.19	Fixed in–

AI-suggested

A fix has been implemented in the Linux kernel to properly save and restore all relevant RX state fields and registrations after a reload failure in the lan966x driver. Users should update to the patched kernel version containing this fix. No additional mitigation steps are indicated.

Description

A vulnerability in the Linux kernel's lan966x network driver was resolved involving improper restoration of RX state after a reload failure. Specifically, certain fields related to RX page geometry and page pool registration were not restored correctly if resource reallocation failed, causing inconsistencies in RX buffer handling. This could lead to the XDP path advertising incorrect frame sizes, potentially causing buffer mismanagement.

Impact

The inconsistent RX state after a failed reload can cause the XDP path to operate with mismatched frame sizes and buffer allocations, which may lead to incorrect packet processing or dropped packets. No active exploits are known, and the impact is limited to RX buffer management inconsistencies within the lan966x network driver.

Summary

The vulnerability in the Linux kernel lan966x driver occurs because lan966x_fdma_reload() backs up some RX state fields before reallocating RX resources for a new MTU but fails to restore all updated fields (rx->page_order and rx->max_mtu) on allocation failure. Consequently, RX may restart with old pages and FDMA state but with page geometry from the failed new MTU, causing the XDP path to advertise a frame size larger than the actual RX pages. Additionally, the rollback path does not restore per-port XDP RXQ memory model registration after fdma_alloc_coherent() failure, leading to inconsistent RX state. The fix involves saving and restoring these fields and registrations to maintain consistent RX state after reload failures.

References

Community reviews

Loading reviews…