CVE-2021-46939 is a deadlock vulnerability in the Linux kernel tracing subsystem. When tracing is recursively re-entered, including through the function graph tracer, trace_clock_global() can acquire the lock protecting its recorded previous timestamp while reserving a ring-buffer event. A traced operation can then re-enter ring_buffer_lock_reserve() and invoke trace_clock_global() again on the same execution path, causing a second attempt to acquire the already-held spinlock. The resulting deadlock can hang the machine. The upstream fix restructures trace_clock_global() to avoid blocking: it uses a trylock when updating the previous timestamp and defers the update if the lock is already held.
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.
Linux kernel tracing flaw corrected by ensuring trace_clock_global() does not block.
Linux kernel tracing issue addressed by preventing trace_clock_global() from blocking.
A Linux kernel tracing vulnerability involving trace_clock_global() potentially blocking; the referenced assessment characterizes the impact as moderate and associates it with lock/deadlock and tracing conditions.
A Linux kernel tracing deadlock vulnerability in trace_clock_global(). Recursive tracing can re-acquire an already-held spin lock, causing a system hang/denial of service. The fix restructures the code to use a trylock when updating prev_time so tracing does not block.
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.