Loading vulnerability…
CVE-2024-36000 is a race condition in the Linux kernel hugetlb memory-management subsystem. During hugetlb reservation uncharging, an unlikely userfaultfd-mediated path can permit concurrent modification of a reservation map without holding hugetlb_lock. The uncharge logic invokes hugetlb_cgroup_uncharge_folio_rsvd(), which updates a cgroup pointer and therefore requires serialization by hugetlb_lock. The upstream fix ensures that the required lock is held for this reservation-uncharge path.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel hugetlb memory-management vulnerability caused by missing hugetlb_lock during reservation uncharge.
Linux hugetlb memory-management locking flaw during reservation uncharge.
Linux kernel HugeTLB memory-management locking flaw during reservation uncharge operations.
A Linux kernel hugetlb memory-management flaw caused by a missing hugetlb_lock during reservation uncharge operations.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.