CVE-2026-0133
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 smmu_attach_dev of arm-smmu-v3.c, there is a possible way to sign malicious Android Runtime bootclass artifacts due to a missing permission check. 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 · high confidenceA missing permission check in the smmu_attach_dev function of the ARM SMMU v3 kernel driver (arm-smmu-v3.c) allows local attackers to sign malicious Android Runtime bootclass artifacts, leading to local privilege escalation without user interaction or additional execution privileges.
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.
-
Identify if ARM SMMU v3 hardware is presentCheck /sys/firmware/devicetree/base or /proc/device-tree for compatible SMMU v3 nodes, or run 'lspci | grep -i smmu' or check 'dmesg | grep -i smmu' for SMMU v3 initialization messagesAffected if The device has ARM SMMU v3 hardware (SMMU-500 or later) present and initialized
-
Verify the arm-smmu-v3 kernel driver is loadedCheck if the module is loaded with 'lsmod | grep arm_smmu' or if it's built into the kernel, check 'cat /sys/module/arm_smmu*/version' or look for 'arm-smmu-v3' in /proc/modulesAffected if The arm-smmu-v3 kernel driver is loaded or built into the running kernel
-
Check if SMMU v3 is enabled in kernel configurationFor the running kernel, check /boot/config-* or /proc/config.gz for CONFIG_ARM_SMMU_V3=y or CONFIG_ARM_SMMU_V3=mAffected if The SMMU v3 driver is enabled in the kernel (CONFIG_ARM_SMMU_V3 is set to y or m)
-
Determine device exposure to the attach_dev interfaceCheck if any userspace processes can access /dev/ arm-smmu-v3 device nodes (ls -la /dev/*smmu* 2>/dev/null) or if the iommu subsystem exposes the SMMU v3 to userspaceAffected if The SMMU v3 device is exposed to userspace or accessible through iommu device nodes that allow attach operations
A device is affected if it has ARM SMMU v3 hardware present with the arm-smmu-v3 driver loaded and the smmu_attach_dev interface exposed to local userspace processes.
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 dataAdd proper permission validation in the smmu_attach_dev function to verify the caller has appropriate privileges before allowing device attachment and artifact signing operations.
- Consultation6.0 h
- Implementation4.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0133 — 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-2026-0133 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