<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Cpe:2.3:o:qualcomm:sd855_firmware:-:*:*:*:*:*:*:* - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/cpes/cpe2.3oqualcommsd855_firmware-/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Sat, 24 Oct 2026 00:02:34 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/cpes/cpe2.3oqualcommsd855_firmware-/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Qualcomm Adreno GPU Privilege Escalation (CVE-2025-21479)</title><link>https://feed.craftedsignal.io/briefs/2026-10-vivo-iqoo-neo9-root-cve-2025-21479/</link><pubDate>Sat, 24 Oct 2026 00:02:34 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-vivo-iqoo-neo9-root-cve-2025-21479/</guid><description>CVE-2025-21479 is a high-severity local privilege escalation vulnerability in the Qualcomm Adreno GPU driver allowing for kernel-level arbitrary physical memory writes, with functional exploits now targeting Android devices including the iQOO Neo9.</description><content:encoded><![CDATA[<p>CVE-2025-21479 is a high-severity vulnerability (CVSS 8.6) in the Qualcomm Adreno GPU driver firmware, specifically related to the <code>CP_SET_DRAW_STATE</code> command. An exploit has been published that leverages this flaw to achieve arbitrary physical memory write access. On the iQOO Neo9 (running Android 15), this is used to gain kernel-level root access by patching kernel memory to enable full process capabilities (41-bit) while deliberately retaining a non-zero effective UID to bypass manufacturer-specific anti-root detection mechanisms like <code>vr.ko</code>.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker executes a local, user-level binary on the target Android device.</li>
<li>The exploit triggers a vulnerability in the Adreno GPU driver (CP_SET_DRAW_STATE).</li>
<li>The GPU driver performs an unauthorized SMMU table update (CP_SMMU_TABLE_UPDATE).</li>
<li>The attacker achieves arbitrary physical write primitive via a forged page table.</li>
<li>The kernel memory is patched to disable <code>kptr_restrict</code> and modify <code>cap_bprm_creds_from_file</code> to preserve capabilities across binary execution.</li>
<li>A resident root daemon is spawned, granting full 41-bit capabilities (CapEff) while maintaining euid=2000 to evade anti-root detection.</li>
<li>The daemon provides a command execution interface for arbitrary root commands.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows local, unprivileged users or malicious applications to gain full kernel-level capabilities on affected Android devices, bypassing system security policies and manufacturer-specific anti-root protections. The exploit is resident in RAM and does not persist across reboots, but provides full system control while active.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Monitor for unauthorized binaries being pushed to <code>/data/local/tmp</code> via ADB or other vectors.</li>
<li>Audit device integrity for signs of active kernel memory modification, particularly those targeting <code>kptr_restrict</code> or capability-related functions.</li>
<li>Prioritize patching Android devices when OEM firmware updates addressing CVE-2025-21479 become available.</li>
<li>Restrict ADB access and developer options in production/managed environments to mitigate the initial deployment vector.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>privilege-escalation</category><category>android</category><category>vulnerability</category><category>mobile-security</category></item></channel></rss>