CVE-2022-20009 is an out-of-bounds write vulnerability in various functions of the Android kernel USB gadget subsystem. A missing bounds check permits a write beyond the intended buffer boundary and can enable local 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 provides a proof-of-concept (POC) exploit for CVE-2022-20009, a buffer overflow vulnerability in certain Android Linux kernel USB gadget drivers (f_accessory, f_audio_source, f_gsi, f_mtp, f_qc_rndis, f_rmnet). The main exploit script, gadget.py, is written in Python and uses the pyusb library to send crafted USB control transfer requests with an oversized wLength field to a physically connected Android device. The exploit requires the host to use a custom build of libusb with an increased MAX_CTRL_BUFFER_LENGTH (0xffff). The script allows the user to specify the target device's vendor and product IDs, the USB gadget function to target, and the length of the data to send. If successful, the exploit can cause a buffer overflow in the kernel, potentially leading to information disclosure, denial of service, or code execution. The repository is structured with a single exploit script, a README.md providing technical details and usage instructions, a LICENSE file, and a .gitignore. No network endpoints are involved; the attack vector is via physical USB connection.
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.