Loading vulnerability…
A use-after-free vulnerability exists in kernel/ucount.c in the Linux kernel versions 5.14 through 5.16.4. When unprivileged user namespaces are enabled, a ucounts object may outlive its associated namespace, leading to a dangling pointer. This can be exploited to achieve privilege escalation.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept (PoC) exploit for CVE-2022-24122, a Linux kernel vulnerability that can be leveraged to cause a Denial of Service (DoS) condition. The exploit is implemented in C (exploit.c) and works by creating and manipulating System V IPC resources, specifically shared memory segments and message queues. It uses process cloning, CPU affinity manipulation, and resource spraying to exhaust or corrupt kernel resources, ultimately triggering the DoS. The exploit is most effective on single-core systems, with reduced reliability on multi-core systems, as noted in the README. The repository structure is simple, containing only a README and the exploit source code. No remote or network attack vector is present; the exploit must be run locally on the target system. The only fingerprintable endpoint is the use of System V shared memory and message queues, which are standard Linux IPC mechanisms.
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.