CVE-2025-48624
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn multiple functions of arm-smmu-v3.c, there is a possible out-of-bounds write due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA memory corruption vulnerability exists in the ARM SMMU v3 driver (arm-smmu-v3.c) where improper input validation in multiple functions allows an out-of-bounds write. This can be exploited locally to escalate privileges to root without requiring additional execution privileges or user interaction.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm ARM architectureRun 'uname -m' or check /proc/cpuinfo for 'ARM' or 'aarch64' architectureAffected if System is running on ARM 64-bit (aarch64) architecture, as SMMU v3 is an ARM-specific hardware IOMMU
-
Identify Android kernelCheck /proc/version or run 'uname -a' to see if the kernel is from Android; also check /system/build.prop for ro.build.fingerprintAffected if Device is running Google Android, which is explicitly listed as affected for all versions
-
Verify arm-smmu-v3 driver presenceCheck kernel config for CONFIG_ARM_SMMU_V3 (grep -i 'ARM_SMMU_V3' /boot/config* or /proc/config.gz) or check if driver is loaded via lsmod | grep arm_smmuAffected if The arm-smmu-v3 driver is compiled into the kernel or loaded as a module; the vulnerability exists in this driver code
-
Check driver source fileLocate arm-smmu-v3.c in the kernel source tree used to build the device kernel; verify if the file contains the vulnerable functions lacking proper input validationAffected if The driver source code has not been patched with bounds checking fixes in the affected functions mentioned in the CVE
-
Determine exploitability contextCheck if the device uses SMMU v3 hardware by examining dmesg for 'arm-smmu-v3' messages or device tree bindings; also verify if the driver handles secure or privileged operationsAffected if The SMMU v3 driver is active and handling IOMMU operations, providing a path for local privilege escalation without additional privileges
A defender is affected if their Android device runs on ARM 64-bit architecture with the arm-smmu-v3 driver present and the kernel has not been patched with the upstream fix for CVE-2025-48624.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the upstream kernel patch for CVE-2025-48624 which adds proper input validation and bounds checking to the affected functions in the arm-smmu-v3.c driver. Ensure kernel updates are deployed to all affected ARM-based systems running this driver.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48624 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-48624 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data