CVE-2026-0133: In smmu_attach_dev of arm-smmu-v3
In 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.
Metrics
- CVSS v3.1
- 7.8
- Severity
- HIGH
- Fixed in
- —
- Affected Products
- 1
HarborGuard Analysis
Synopsis
This is a missing permission check vulnerability in the ARM SMMU v3 driver (smmu_attach_dev in arm-smmu-v3.c) in the Android kernel. An attacker with a local shell and low-privilege account can exploit the flaw without any user interaction, allowing them to sign malicious Android Runtime bootclass artifacts. Successful exploitation leads to local escalation of privilege, giving the attacker elevated control over the affected device. HarborGuard is tracking this advisory and will make a patched-image rebuild available as soon as an upstream fix is published.
HarborGuard Coverage
Detection for CVE-2026-0133 is available across every HarborGuard environment: the CVE is ingested from upstream advisory feeds within minutes of publication and matched against customer images, including custom-built Android kernel images in any connected registry or CI pipeline.
AvailableHarborGuard is capable of scoring this CVE at 7.8 HIGH (CVSS v3.1) against each affected image, weighting it further against per-environment compliance policies, and routing the finding to the appropriate team inbox within each customer organization.
AvailableBecause no fix version has been published upstream, HarborGuard re-checks this advisory on every ingest cycle and will make a patched-image rebuild available automatically the moment Google ships a remediated kernel release. In the meantime, compensating controls such as network-policy isolation and reduced attack-surface configurations can be applied to limit exposure.
Pending upstreamExploit Conditions
- Network reachabilityNot required
The attacker needs an existing shell or process on the host; no network access to the device is required to trigger the flaw.
- AuthenticationRequired
Any low-privilege local account is sufficient; no administrative or elevated credentials are needed before exploitation.
- Victim interactionNot required
No user action, click, or social-engineering step is required; the attacker can exploit the flaw entirely on their own.
- Attack complexityDetail
Exploitation is reliable and condition-free; no race conditions or specific memory-layout requirements must be satisfied.
Blast Radius
- A successful attacker signs malicious Android Runtime bootclass artifacts, allowing persistent tampered code to run as part of the trusted boot environment.
- The attacker reads sensitive data accessible at elevated privilege, including credentials, tokens, and protected application data stored on the device.
- The attacker modifies system files, persisted configurations, and trusted class hierarchies that govern runtime behavior across the device.
- Full confidentiality, integrity, and availability of the affected Android kernel environment are compromised, meaning the device should be treated as untrustworthy until remediated.
How HarborGuard Handles This
Available on HarborGuard: detection for CVE-2026-0133 is active now, matching this CVE against any Android kernel image in customer registries and pipelines. Because Google has not yet published a fix version, no patched-image rebuild is available at this time. HarborGuard re-checks the advisory on every ingest cycle and will automatically trigger a rebuild and, for customers with auto-remediation enabled, open a patch PR against affected workloads the moment an upstream fix is released. While waiting for a patch, customers can reduce exposure by applying strict network-policy isolation around affected workloads, enabling egress filtering to limit lateral movement from any compromised process, and auditing which low-privilege accounts have access to affected container environments. Where compliance policy permits, customers may also consider restricting runtime execution contexts that interact with SMMU device attachment paths.
- Google / AndroidAndroid kernel
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H