Loading vulnerability…
CVE-2025-25177 is a high-severity vulnerability affecting Imagination PowerVR GPU components on Android. The issue is described as allowing software running as a non-privileged user to perform improper GPU system calls that trigger a use-after-free condition in the kernel. This indicates a flaw in the lifetime management of kernel-side GPU-related objects or memory referenced through the graphics stack, where a previously freed resource can still be accessed after attacker-controlled interaction with the GPU driver interface. Because the vulnerable condition is reachable from an unprivileged context through GPU system-call handling, a malicious local application may be able to induce kernel exceptions and potentially influence subsequent kernel behavior depending on allocator state and execution timing.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
High-severity vulnerability impacting Imagination PowerVR GPU components (GPU driver class issues such as memory corruption/information disclosure/local privilege escalation are mentioned generally).
Imagination PowerVR GPU vulnerability fixed via vendor updates; may enable data leakage or execution paths via malicious GPU workloads.
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.