CVE-2026-80729
mm/huge_memory: initialise workingset state before folio split
Description
In the Linux kernel, the following vulnerability has been resolved: mm/huge_memory: initialise workingset state before folio split xas_try_split() adds __GFP_ACCOUNT for page-cache xa_nodes, but __folio_split() leaves the xa_state's xa_lru unset. That lets a live, memcg-charged xa_node exist without being linked into the mapping's shadow_nodes list_lru; when reclaim later walks the list_lru it trips VM_WARN_ON(!css_is_dying()). Use mapping_set_update() to install both the workingset update callback and the shadow_nodes list_lru on the xa_state.
INFO
Published Date :
Sept. 3, 2026, 8:21 a.m.
Last Modified :
Sept. 3, 2026, 8:21 a.m.
Remotely Exploit :
No
Source :
Linux
Solution
- Apply the kernel patch for huge_memory: initialise workingset state.
- Update the Linux kernel to the latest stable version.
- Ensure workingset state is correctly initialized before folio splits.
- Verify shadow_nodes list_lru is updated by mapping_set_update().
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-80729 vulnerability anywhere in the article.