Loading vulnerability…
CVE-2022-22063 is a memory corruption vulnerability in the Core component, caused by improper configuration in the boot remapper. The flaw allows for unintended memory manipulation, potentially leading to system instability or code execution.
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-22063, a critical privilege escalation vulnerability in the hypervisor firmware of certain Qualcomm chipsets (notably Snapdragon 410/MSM8916 and similar). The vulnerability arises from an unprotected hardware register (APCS_BOOT_START_ADDR_NSEC) that allows the operating system kernel to remap and overwrite hypervisor memory, bypassing isolation mechanisms. The main exploit code is in 'CVE-2022-22063.c', which demonstrates how to use this register to inject shellcode into the hypervisor's exception vector table, disable its protections, and execute arbitrary code at the hypervisor level (EL2). The repository also includes a patch (LK.diff) for integrating the exploit as a fastboot OEM command, a README with detailed technical background, and several SVG diagrams illustrating the ARM exception levels, memory layout, and the boot remapper mechanism. The exploit is a local privilege escalation and requires kernel-level access on a vulnerable device. It is a PoC and does not include weaponized or automated payloads, but demonstrates the full attack chain from kernel to hypervisor compromise.
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.