Loading vulnerability…
A vulnerability in the Linux kernel's fs/proc implementation, specifically in the do_task_stat() function, allowed a scenario where lock_task_sighand() could trigger a hard lockup. If NR_CPUS threads simultaneously invoked do_task_stat() on a process with NR_THREADS, the system could spin with interrupts disabled for O(NR_CPUS * NR_THREADS) time, leading to a denial of service condition. The issue was resolved by changing do_task_stat() to use sig->stats_lock for gathering thread and child statistics outside the ->siglock protected section, reducing the risk of lock contention and hard lockups.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel procfs task-statistics synchronization issue fixed by using sig->stats_lock while gathering thread and child statistics.
Linux kernel procfs task-statistics synchronization issue addressed by using sig->stats_lock when collecting thread and child statistics.
Linux kernel procfs task-statistics locking issue.
Linux procfs do_task_stat synchronization flaw affecting thread and child statistics gathering.
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.