Loading vulnerability…
CVE-2025-39843 is a Linux kernel mm/SLUB locking flaw in the debug-object allocation path. When set_track_prepare() is reached from hrtimer_start_range_ns() while a per-CPU hrtimer base lock is held, an allocation associated with timer debug objects can implicitly wake kswapd. The kswapd wakeup path can attempt to acquire the same hrtimer-base lock, causing spinlock recursion and deadlock. The fix supplies constrained allocation flags to the debug_objects_fill_pool() path that exclude __GFP_KSWAPD_RECLAIM and masks __GFP_DIRECT_RECLAIM in ___slab_alloc(), where preemption is disabled.
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.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel vulnerability in the memory management SLUB area related to set_track_prepare().
A Linux kernel mm/slub vulnerability fixed by avoiding wake up of kswapd in set_track_prepare.
A Linux kernel SLUB memory-management issue involving unnecessary kswapd wakeups in set_track_prepare, addressed by the Red Hat kernel security update.
A Linux kernel SLUB memory-management/debug-objects locking flaw that can cause spinlock recursion and deadlock when timer debug-object tracking triggers memory allocation and an implicit kswapd wakeup while an hrtimer-base lock is held.
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.