RX state inconsistency via incomplete MTU rollback
Published Oct 23, 2026 · Updated Oct 23, 2026
RX state corruption in the Linux lan966x driver allows attackers to leave XDP using mismatched buffers after a failed MTU change. The lan966x_fdma_reload() rollback restores old RX allocations without restoring page_order, max_mtu, or each port's XDP page-pool registration, leaving frame geometry or memory registration inconsistent. Reaching this state requires LAN966x hardware and an allocation failure during MTU reload; public evidence establishes neither a specific crash nor arbitrary code execution.
Summary
What happened
RX state corruption in the Linux lan966x driver allows attackers to leave XDP using mismatched buffers after a failed MTU change. The lan966x_fdma_reload() rollback restores old RX allocations without restoring page_order, max_mtu, or each port's XDP page-pool registration, leaving frame geometry or memory registration inconsistent. Reaching this state requires LAN966x hardware and an allocation failure during MTU reload; public evidence establishes neither a specific crash nor arbitrary code execution.
The record
- CVE
- CVE-2026-98906
- Published
- Oct 23, 2026
- Updated
- Oct 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 23, 2026CVE publishedPublication date reported by the CVE source.
- Oct 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <6.12.111
- Affected versionversion=0 <6.18.53
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3883898ddc26308497dbba8068951ab5eddbd111
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <aa97f11a76e545ed73cc455bcdd1ece4b480b507
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b5a6462f4646687c922931133a2478da94addc87
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us