Loading vulnerability…
A vulnerability in the __secure_computing function in kernel/seccomp.c of the Linux kernel (versions 2.6.28.7 and earlier) on x86_64 platforms allows local users to bypass seccomp access restrictions. The flaw occurs when CONFIG_SECCOMP is enabled and the kernel does not correctly handle cross-architecture syscalls: specifically, 32-bit processes making 64-bit syscalls or 64-bit processes making 32-bit syscalls. This can result in syscalls being misinterpreted, such as stat or chmod, allowing restricted operations to be performed. This issue is related to CVE-2009-0342 and CVE-2009-0343.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.