{"id":"CVE-2026-98906","title":"net: lan966x: restore RX state on reload failure","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet: lan966x: restore RX state on reload failure\n\nlan966x_fdma_reload() backs up rx->page_pool and rx->fdma before\nreallocating the RX resources for the new MTU. If the…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 3883898ddc26308497dbba8068951ab5eddbd111","Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < b5a6462f4646687c922931133a2478da94addc87","Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < aa97f11a76e545ed73cc455bcdd1ece4b480b507","Linux < 6.12.111","Linux < 6.18.53","Linux (all versions)"],"published":"2026-10-23","updated":"2026-10-23","sourceUpdated":"2026-10-23T11:54:42.697Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-98906","references":[{"url":"https://git.kernel.org/stable/c/3883898ddc26308497dbba8068951ab5eddbd111"},{"url":"https://git.kernel.org/stable/c/b5a6462f4646687c922931133a2478da94addc87"},{"url":"https://git.kernel.org/stable/c/aa97f11a76e545ed73cc455bcdd1ece4b480b507"}],"tags":["cve.org"],"ingestedAt":"2026-10-23T13:24:55.574Z","slug":"CVE-2026-98906","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: lan966x: restore RX state on reload failure\n\nlan966x_fdma_reload() backs up rx->page_pool and rx->fdma before\nreallocating the RX resources for the new MTU. If the allocation fails,\nthe restore path puts these fields back before restarting RX.\n\nHowever, the reload path also updates rx->page_order and rx->max_mtu\nbefore calling lan966x_fdma_rx_alloc(). These fields are not restored on\nfailure, so RX can be restarted with the old pages, old FDMA state and\nold page pool, but with the page geometry from the failed new MTU.\n\nThis can make the XDP path advertise a frame size derived from the new\npage_order while the actual RX pages still come from the old allocation.\nFor example, after a failed reload to a jumbo MTU, xdp_init_buff() may be\ncalled with a frame size larger than the restored RX pages.\n\nlan966x_fdma_rx_alloc_page_pool() also registers the newly allocated page\npool with each port's XDP RXQ before fdma_alloc_coherent() is called. If\nfdma_alloc_coherent() fails, the new page pool is destroyed, but the\nrollback path does not restore the per-port XDP RXQ mem model\nregistration either.\n\nSave and restore rx->page_order and rx->max_mtu, and restore the old page\npool registration for each port's XDP RXQ before RX is started again.\nThis keeps the restored RX state consistent after a failed reload.\n\n## Affected\n\n- `Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 3883898ddc26308497dbba8068951ab5eddbd111`\n- `Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < b5a6462f4646687c922931133a2478da94addc87`\n- `Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < aa97f11a76e545ed73cc455bcdd1ece4b480b507`\n- `Linux < 6.12.111`\n- `Linux < 6.18.53`\n- `Linux (all versions)`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}