Loading vulnerability…
A use-after-free vulnerability exists in the Linux kernel's io_uring subsystem (fs/io_uring.c) prior to version 5.17.3. The flaw is due to a race condition in the handling of io_uring timeouts, which can be triggered by a local user, even without access to any user namespace. The vulnerability arises when concurrent operations on io_uring timeouts lead to a situation where memory is freed and subsequently accessed, resulting in undefined behavior.
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 working exploit for CVE-2022-29582, a local privilege escalation vulnerability in the Linux kernel's io_uring subsystem. The exploit is written in C and is designed to be built statically, with the main entry point being the 'bin/exp' binary produced by the Makefile. The exploit leverages custom cache manipulation logic (cross_cache.c/h) and interacts with the io_uring subsystem via the included liburing library. The repository also includes a full copy of the liburing library, its documentation, and several example programs demonstrating io_uring usage, but the exploit itself is independent and focused on the vulnerability. The README provides build and usage instructions, specifying that the exploit targets kernel version 5.10.90 and works with the kCTF setup. The attack vector is local, requiring the attacker to execute code on the target system. No network endpoints or remote attack surfaces are present. The exploit is operational, providing a working local privilege escalation if run on a vulnerable system.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.