CVE-2022-20409 is a use-after-free vulnerability in the Android kernel's io_uring component, specifically in io_identity_cow. The flaw can corrupt memory and may enable local elevation of privilege. Exploitation requires System execution privileges and does not require user interaction.
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 local privilege escalation exploit targeting Android devices, specifically Google Pixel 6 and Samsung Galaxy S22, by abusing a vulnerability in the Linux kernel's io_uring subsystem. The main exploit logic is implemented in two C files: exp_pixel6.c and exp_s22.c, each tailored for the respective device. The exploit requires the attacker to extract the kernel symbol table from the device's boot image, using provided tools (unpack_bootimg.py and vmlinux-to-elf), and then run the compiled exploit binary on the device with the symbol file as an argument. If successful, the exploit grants a root shell. The repository also includes build scripts for Android NDK, and helper tools for kernel image and symbol extraction. The attack vector is local, requiring code execution on the device. No network endpoints are involved, but several fingerprintable file paths (such as /data/local/tmp and boot.img) are used in the exploitation process. The exploit is operational and provides a working root shell payload, but is not part of a larger exploitation framework.
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 and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.