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.

An update of the linux package has been released.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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.
    (CVE-2026-98906)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Type	Severity
376443	Ubuntu 24.04 LTS / 26.04 LTS : Linux kernel vulnerabilities (USN-8959-1)	Nessus	Ubuntu Local Security Checks	Local	high
375113	Photon OS 5.0: Linux PHSA-2026-5.0-91-1014	Nessus	PhotonOS Local Security Checks	Local	high
375014	Photon OS 5.0: Linux PHSA-2026-5.0-92-1014	Nessus	PhotonOS Local Security Checks	Local	high
371535	Linux Distros Unpatched Vulnerability : CVE-2026-98906	Nessus	Misc.	Local	medium

Detections

Analytics

CVE-2026-98906

high

Tenable Plugins

high

high

high

medium