CVE-2026-31644: net: lan966x: fix use-after-free and leak in lan966x_fdma_reload()
In the Linux kernel, the following vulnerability has been resolved:
net: lan966x: fix use-after-free and leak in lan966x_fdma_reload()
When lan966x_fdma_reload() fails to allocate new RX buffers, the restore
path restarts DMA using old descriptors whose pages were already freed
via lan966x_fdma_rx_free_pages(). Since page_pool_put_full_page() can
release pages back to the buddy allocator, the hardware may DMA into
memory now owned by other kernel subsystems.
Additionally, on the restore path, the newly created page pool (if
allocation partially succeeded) is overwritten without being destroyed,
leaking it.
Fix both issues by deferring the release of old pages until after the
new allocation succeeds. Save the old page array before the allocation
so old pages can be freed on the success path. On the failure path, the
old descriptors, pages and page pool are all still valid, making the
restore safe. Also ensure the restore path re-enables NAPI and wakes
the netdev, matching the success path.
Security readout for executives and security teams
Plain-English summary
A failure while reloading the Linux LAN966x network driver can leave network hardware writing into kernel memory that has already been reassigned. This could corrupt sensitive data, crash the system, or compromise kernel integrity. A separate failure-path resource leak is also fixed.
Executive priority
Treat as a high-priority kernel maintenance issue for systems using LAN966x networking, especially shared or security-sensitive infrastructure. It is not evidence of an internet-wide emergency: the supplied assessment requires local access, and no active exploitation is documented.
Technical view
In lan966x_fdma_reload(), failed RX-buffer allocation could restart DMA with descriptors referencing pages already returned through page_pool_put_full_page(). The device could then overwrite memory owned by other kernel subsystems. The correction retains old pages and the page pool until replacement allocation succeeds, and restores NAPI and net-device state consistently.
Likely exposure
Exposure requires a Linux system using the LAN966x network driver and reaching the vulnerable FDMA reload failure path. The supplied version data identifies affected Linux releases but is ambiguous about exact ranges; validate the running kernel against vendor advisories and the referenced stable fixes.
Exploitation context
The CVSS vector describes local access, low privileges, low complexity, and no user interaction, with potentially high confidentiality, integrity, and availability impact. The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or a public exploit.
Researcher notes
The safety impact comes from device DMA continuing through stale RX descriptors after page release, creating a kernel use-after-free condition with cross-subsystem corruption potential. The restore path could also leak a partially created page pool. Exact affected and fixed release boundaries cannot be confidently reconstructed from the supplied version fields.
Mitigation direction
Update to a vendor-supported kernel containing the applicable referenced stable fix.
Check distribution or appliance guidance for precise fixed versions before scheduling deployment.
Prioritize affected multi-user, edge, or network infrastructure where local account compromise is consequential.
Use normal kernel rollback and recovery planning because remediation changes kernel code.
Validation and detection
Confirm whether the LAN966x driver and corresponding hardware are present and operational.
Record the running kernel build and compare it with vendor-fixed package information.
Verify the installed kernel incorporates the applicable referenced stable commit.
After updating, confirm the expected kernel is running and network interfaces operate normally.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-31644 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
5Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.