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

In the Linux kernel, the following vulnerability has been resolved:

net: lan966x: restore RX state on reload failure

lan966xfdmareload() backs up rx->pagepool 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->pageorder and rx->maxmtu before calling lan966xfdmarxalloc(). 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 pageorder while the actual RX pages still come from the old allocation. For example, after a failed reload to a jumbo MTU, xdpinitbuff() may be called with a frame size larger than the restored RX pages.

lan966xfdmarxallocpagepool() also registers the newly allocated page pool with each port's XDP RXQ before fdmaalloccoherent() is called. If fdmaalloccoherent() 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->pageorder and rx->maxmtu, 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.