CVE-2026-74573

CRITICALPre-NVD 9.39.3—
EchelonGraph scoreHIGH confidence

Score 9.3 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-15. a secondary CVSS source baseline 9.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
9.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

iommu/arm-smmu-v3-iommufd: Require exactly one Stream ID for a vDEVICE

arm_vsmmu_vsid_to_sid() maps a guest's vSID to a single physical Stream ID taken from master->streams[0], assuming a device has exactly one stream. A device with several streams gets only its first one mapped, so a guest vSID invalidation cannot reach the others' ATC and IOTLB entries; a device with none makes master->streams a ZERO_SIZE_PTR, read out of bounds.

Add an arm_vsmmu_vdevice_init() op to reject the vDEVICE with -EOPNOTSUPP when master->num_streams is not one, rather than mapping it silently.

CVSS v3
9.3
EG Score
9.3(high)
EG Risk
46(Track)
EG Risk 46/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 computed
Severity93% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (3)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

iommu/arm-smmu-v3-iommufd: Require exactly one Stream ID for a vDEVICE - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c3b8ee84a965058b41275069d4696f37a8b14bf6
generic

iommu/arm-smmu-v3-iommufd: Require exactly one Stream ID for a vDEVICE - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3808bab5d95ae79e333e11f6a73d178e084c645d
generic

iommu/arm-smmu-v3-iommufd: Require exactly one Stream ID for a vDEVICE - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0acbc621341aca4eb94d9c2f43e1ab273ff088f0

Vendor Advisories for CVE-2026-74573(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 42× in last 7d / 42× 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.

  1. 2026-08-20 18:41 UTCGHSA enrichment
  2. 2026-08-20 14:43 UTCGHSA enrichment
  3. 2026-08-20 10:44 UTCGHSA enrichment
  4. 2026-08-20 06:45 UTCGHSA enrichment
  5. 2026-08-20 02:46 UTCGHSA enrichment
  6. 2026-08-19 22:47 UTCGHSA enrichment
  7. 2026-08-19 18:48 UTCEG score recompute
  8. 2026-08-19 18:48 UTCGHSA enrichment
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-19 14:49 UTCGHSA enrichment
  11. 2026-08-19 10:51 UTCGHSA enrichment
  12. 2026-08-19 06:53 UTCGHSA enrichment
  13. 2026-08-19 02:54 UTCGHSA enrichment
  14. 2026-08-18 22:54 UTCGHSA enrichment
  15. 2026-08-18 18:56 UTCGHSA enrichment
  16. 2026-08-18 14:57 UTCEG score recompute
  17. 2026-08-18 14:57 UTCGHSA enrichment
  18. 2026-08-18 13:49 UTCEPSS rescore
  19. 2026-08-18 13:49 UTCEPSS rescore
  20. 2026-08-18 10:47 UTCGHSA enrichment
  21. 2026-08-18 06:49 UTCGHSA enrichment
  22. 2026-08-18 02:50 UTCGHSA enrichment
  23. 2026-08-17 22:52 UTCGHSA enrichment
  24. 2026-08-17 18:53 UTCGHSA enrichment
  25. 2026-08-17 14:20 UTCEG score recompute
Show 17 more
  1. 2026-08-17 14:20 UTCGHSA enrichment
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-17 10:21 UTCEG score recompute
  4. 2026-08-17 10:21 UTCGHSA enrichment
  5. 2026-08-17 06:23 UTCEG score recompute
  6. 2026-08-17 06:23 UTCGHSA enrichment
  7. 2026-08-17 05:54 UTCEG score recompute▲ 9.30
  8. 2026-08-17 05:54 UTCGHSA enrichment
  9. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 9.3 · severity → CRITICAL
  10. 2026-08-17 05:39 UTCEG score recompute
  11. 2026-08-17 05:39 UTCGHSA enrichment
  12. 2026-08-17 05:39 UTCMITRE cvelistV5
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-15 13:27 UTCNVD update
  16. 2026-08-15 12:38 UTCEG score recompute
  17. 2026-08-15 12:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74573?
CVE-2026-74573 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: iommu/arm-smmu-v3-iommufd: Require exactly one Stream ID for a vDEVICE armvsmmuvsidtosid() maps a guest's vSID to a single physical Stream ID taken from master->streams[0], assuming a device has exactly one stream. A device with…
When was CVE-2026-74573 disclosed?
CVE-2026-74573 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74573 actively exploited?
CVE-2026-74573 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.9% of all scored CVEs.
What is the CVSS score of CVE-2026-74573?
CVE-2026-74573 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-74573?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74573, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-74573

Explore →

Is Your Infrastructure Affected by CVE-2026-74573?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs