CVE-2026-53057

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 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/riscv: Add IOTINVAL after updating DDT/PDT entries

Add riscv_iommu_iodir_iotinval() to perform required TLB and context cache invalidations after updating DDT or PDT entries, as mandated by the RISC-V IOMMU specification (Section 6.3.1 and 6.3.2).

CVSS v3
8.8
EG Score
8.8(high)
EPSS
2.7%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 28, 2026

Advisory Details (3)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

iommu/riscv: Add IOTINVAL after updating DDT/PDT entries - kernel/git/stable/linux.git - Linux kernel stable tree

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

iommu/riscv: Add IOTINVAL after updating DDT/PDT entries - kernel/git/stable/linux.git - Linux kernel stable tree

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

iommu/riscv: Add IOTINVAL after updating DDT/PDT entries - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3f917d9bff68600f77561900f3145bd4706dc840

Vendor Advisories for CVE-2026-53057(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 35× in last 7d / 47× 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-07-06 23:20 UTCEG score recompute
  2. 2026-07-06 23:20 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 12:13 UTCEG score recompute
  6. 2026-07-06 12:13 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-06 00:41 UTCEG score recompute
  10. 2026-07-06 00:41 UTCGHSA enrichment
  11. 2026-07-05 13:34 UTCEG score recompute
  12. 2026-07-05 13:34 UTCGHSA enrichment
  13. 2026-07-05 02:27 UTCEG score recompute
  14. 2026-07-05 02:27 UTCGHSA enrichment
  15. 2026-07-04 15:20 UTCEG score recompute
  16. 2026-07-04 15:19 UTCGHSA enrichment
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-04 04:10 UTCEG score recompute
  19. 2026-07-04 04:10 UTCGHSA enrichment
  20. 2026-07-03 17:00 UTCEG score recompute
  21. 2026-07-03 17:00 UTCGHSA enrichment
  22. 2026-07-03 05:53 UTCEG score recompute
  23. 2026-07-03 05:53 UTCGHSA enrichment
  24. 2026-07-02 18:41 UTCEG score recompute
  25. 2026-07-02 18:41 UTCGHSA enrichment
Show 22 more
  1. 2026-07-02 07:35 UTCEG score recompute
  2. 2026-07-02 07:35 UTCGHSA enrichment
  3. 2026-07-01 20:28 UTCEG score recompute
  4. 2026-07-01 20:28 UTCGHSA enrichment
  5. 2026-07-01 15:07 UTCEPSS rescore
  6. 2026-07-01 09:21 UTCEG score recompute
  7. 2026-07-01 09:21 UTCGHSA enrichment
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-30 22:13 UTCEG score recompute▲ 8.80
  10. 2026-06-30 22:13 UTCGHSA enrichment
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-28 14:07 UTCEPSS rescore
  14. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-27 20:15 UTCEG score recompute
  18. 2026-06-27 20:15 UTCGHSA enrichment
  19. 2026-06-27 03:08 UTCEPSS rescore
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-24 18:16 UTCEG score recompute
  22. 2026-06-24 18:03 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-53057?
CVE-2026-53057 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: iommu/riscv: Add IOTINVAL after updating DDT/PDT entries Add riscviommuiodir_iotinval() to perform required TLB and context cache invalidations after updating DDT or PDT entries, as mandated by the RISC-V IOMMU specification…
When was CVE-2026-53057 disclosed?
CVE-2026-53057 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53057 actively exploited?
CVE-2026-53057 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53057?
CVE-2026-53057 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-53057?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53057, 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-53057

Explore →

Is Your Infrastructure Affected by CVE-2026-53057?

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

Start Free Scan →Browse All CVEs