CVE-2024-26686 is an improper resource-locking vulnerability in the Linux kernel's procfs do_task_stat() function. When NR_CPUS threads concurrently collect statistics for a process with NR_THREADS threads, lock_task_sighand() can cause spinning with interrupts disabled for O(NR_CPUS * NR_THREADS) time. Excessive contention in the siglock-protected statistics collection can trigger a hard lockup and render the kernel unresponsive.
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.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A local denial-of-service vulnerability in the Linux kernel's fs/proc do_task_stat() implementation. Concurrent calls can cause excessive spinning with interrupts disabled, resulting in a hard lockup. The reference assigns CVSS v3 severity 5.5 (Medium), requiring low privileges and affecting availability without confidentiality or integrity impact. Google COS kernel packages are addressed by updating to version 18613.164.4 or later.
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.
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.