In multiple functions of arm-smmu-v3.c, there is a possible escalation of privilege due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
CVE-2026-58766
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-15. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(high)
- EG Risk
- 35(Track)EG Risk 35/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity78% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 0%
- KEV
- Not listed
Published
September 15, 2026
Last Modified
September 18, 2026
Advisory Details (1)
Auto-updated Sep 15, 2026Pixel Update Bulletin—September 2026 | Android Open Source Project
https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-01Vendor Advisories for CVE-2026-58766(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 20× in last 7d / 20× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 12:06 UTCGHSA enrichment
- 2026-09-19 00:34 UTCGHSA enrichment
- 2026-09-18 13:02 UTCGHSA enrichment
- 2026-09-18 06:51 UTCEG score recompute
- 2026-09-18 06:51 UTCGHSA enrichment
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-17 19:18 UTCGHSA enrichment
- 2026-09-17 07:06 UTCGHSA enrichment
- 2026-09-16 19:33 UTCGHSA enrichment
- 2026-09-16 15:57 UTCEG score recompute
- 2026-09-16 15:57 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 04:25 UTCGHSA enrichment
- 2026-09-16 04:07 UTCEG score recompute
- 2026-09-16 04:06 UTCGHSA enrichment
- 2026-09-15 19:34 UTCEG score recompute▲ 7.80
- 2026-09-15 19:32 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
- 2026-09-15 19:32 UTCNVD update
- 2026-09-15 18:48 UTCEG score recompute
- 2026-09-15 18:47 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-58766?
When was CVE-2026-58766 disclosed?
Is CVE-2026-58766 actively exploited?
What is the CVSS score of CVE-2026-58766?
How do I remediate CVE-2026-58766?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-58766
Is Your Infrastructure Affected by CVE-2026-58766?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.