Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Out-of-bounds write in Android Kernel arm-smmu-v3 IOMMU

IdentifiersCVE-2025-48624CWE-787· Out-of-bounds Write

CVE-2025-48624 is a critical local elevation-of-privilege vulnerability in the Android kernel IOMMU subsystem, specifically in multiple functions of arm-smmu-v3.c. The issue is caused by improper input validation that can result in an out-of-bounds write. According to the provided bulletin text, successful exploitation does not require user interaction or additional execution privileges. The flaw is listed in the December 2025 Android Security Bulletin as affecting the kernel IOMMU component at the 2025-12-05 patch level.

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A successful exploit can lead to local escalation of privilege on the affected Android device. Because the bug is an out-of-bounds write in a kernel IOMMU component, exploitation may allow an attacker to corrupt kernel memory and break intended isolation boundaries, resulting in compromise of higher-privileged execution context on the device.

Mitigation

If you can’t patch tonight, do this now.

The primary mitigation is prompt installation of the December 2025 Android security update at patch level 2025-12-05 or later. Where immediate patching is not possible, reduce exposure by limiting execution of untrusted local code and applications on affected devices, since the vulnerability is locally exploitable. No specific workaround beyond applying the vendor/kernel fix is provided in the supplied content.

Remediation

Patch, then assume compromise.

Apply the fixes included in the Android December 2025 security updates, specifically the 2025-12-05 security patch level or later, which includes kernel and vendor-specific fixes covering CVE-2025-48624. Device manufacturers should integrate the corresponding kernel patch for the arm-smmu-v3 IOMMU issue and ship an updated build with the appropriate Android security patch string.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleAndroidoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity4

Community discussion across Reddit, Mastodon, and other social sources.