Loading vulnerability…
CVE-2010-1437 is a local Linux kernel vulnerability in the key management subsystem, specifically involving a race condition in the find_keyring_by_name function in security/keys/keyring.c. In Linux kernel 2.6.34-rc5 and earlier, keyctl session operations can race with key_cleanup while a keyring is being deleted, causing code to access a dead keyring object after it has begun teardown. This results in a use-after-free condition that can corrupt memory and crash the system, with the possibility of additional unspecified impact depending on allocator state and execution timing.
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 valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A use-after-free vulnerability involving access to an object after it has effectively been deleted and is being cleaned up.
A use-after-free vulnerability involving access to an object after it has effectively been deleted and is being cleaned up.
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.