Loading vulnerability…
CVE-2024-26645 is a race condition in the Linux kernel tracing subsystem's tracing_map insertion path. When inserting an element for a new key, the kernel initializes the element key and then publishes the element pointer. On weakly ordered multiprocessor architectures, another CPU can observe the published pointer before the preceding key initialization is visible. It can consequently fail to match an existing key and insert a duplicate tracing-map entry. The defect was introduced in Linux kernel 4.17. The fix orders key initialization before pointer publication with a write barrier and uses WRITE_ONCE() to publish the pointer, pairing with the existing READ_ONCE() lookup.
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 map synchronization flaw.
Linux kernel tracing_map issue addressed by ensuring visibility when an element is inserted.
A low-impact Linux kernel tracing_map concurrency/visibility issue involving insertion of tracing-map elements. It was resolved upstream and subsequently addressed through Fedora stable kernel updates and Red Hat Enterprise Linux errata.
A Linux kernel tracing_map race-condition vulnerability (CWE-362) involving visibility when inserting map elements. It can cause availability impact, including resource exhaustion, instability, or denial of service.
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.