CVE-2026-53057

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

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(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

June 24, 2026

Last Modified

August 5, 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.

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-30ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1—

All Vendor Advisories

(8)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Showing the most recent 100 of 255 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-06 13:47 UTCEPSS rescore
  5. 2026-09-04 05:06 UTCEPSS rescore
  6. 2026-09-02 14:12 UTCEPSS rescore
  7. 2026-09-01 13:54 UTCEPSS rescore
  8. 2026-09-01 04:40 UTCEPSS rescore
  9. 2026-08-30 20:04 UTCEG score recompute
  10. 2026-08-30 20:04 UTCVendor advisory
  11. 2026-08-30 20:04 UTCGHSA enrichment
  12. 2026-08-30 19:17 UTCEPSS rescore
  13. 2026-08-30 01:22 UTCEPSS rescore
  14. 2026-08-28 21:41 UTCEPSS rescore
  15. 2026-08-28 03:48 UTCEG score recompute
  16. 2026-08-28 03:48 UTCVendor advisory
  17. 2026-08-28 03:48 UTCGHSA enrichment
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-25 00:46 UTCEG score recompute
  22. 2026-08-25 00:46 UTCVendor advisory
  23. 2026-08-25 00:46 UTCGHSA enrichment
  24. 2026-08-24 13:39 UTCEG score recompute
  25. 2026-08-24 13:39 UTCVendor advisory
Show 75 more
  1. 2026-08-24 13:39 UTCGHSA enrichment
  2. 2026-08-23 20:57 UTCVendor advisory
  3. 2026-08-23 20:57 UTCGHSA enrichment
  4. 2026-08-23 09:50 UTCEG score recompute
  5. 2026-08-23 09:50 UTCVendor advisory
  6. 2026-08-23 09:50 UTCGHSA enrichment
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-22 22:43 UTCVendor advisory
  9. 2026-08-22 22:43 UTCGHSA enrichment
  10. 2026-08-22 11:36 UTCEG score recompute
  11. 2026-08-22 11:36 UTCVendor advisory
  12. 2026-08-22 11:36 UTCGHSA enrichment
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 17:28 UTCVendor advisory
  15. 2026-08-21 17:28 UTCGHSA enrichment
  16. 2026-08-21 05:37 UTCEG score recompute
  17. 2026-08-21 05:37 UTCVendor advisory
  18. 2026-08-21 05:37 UTCGHSA enrichment
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-20 18:30 UTCVendor advisory
  21. 2026-08-20 18:30 UTCGHSA enrichment
  22. 2026-08-20 07:23 UTCEG score recompute
  23. 2026-08-20 07:23 UTCVendor advisory
  24. 2026-08-20 07:23 UTCGHSA enrichment
  25. 2026-08-19 17:04 UTCEPSS rescore
  26. 2026-08-19 13:12 UTCVendor advisory
  27. 2026-08-19 13:12 UTCGHSA enrichment
  28. 2026-08-19 02:05 UTCEG score recompute
  29. 2026-08-19 02:05 UTCVendor advisory
  30. 2026-08-19 02:05 UTCGHSA enrichment
  31. 2026-08-18 13:48 UTCEPSS rescore
  32. 2026-08-17 13:47 UTCEPSS rescore
  33. 2026-08-17 07:14 UTCVendor advisory
  34. 2026-08-17 07:14 UTCGHSA enrichment
  35. 2026-08-16 20:08 UTCEG score recompute
  36. 2026-08-16 20:08 UTCVendor advisory
  37. 2026-08-16 20:08 UTCGHSA enrichment
  38. 2026-08-16 14:56 UTCEPSS rescore
  39. 2026-08-16 07:48 UTCEG score recompute
  40. 2026-08-16 07:48 UTCVendor advisory
  41. 2026-08-16 07:48 UTCGHSA enrichment
  42. 2026-08-16 02:14 UTCEPSS rescore
  43. 2026-08-15 20:42 UTCVendor advisory
  44. 2026-08-15 20:42 UTCGHSA enrichment
  45. 2026-08-15 08:40 UTCEG score recompute
  46. 2026-08-15 08:40 UTCVendor advisory
  47. 2026-08-15 08:40 UTCGHSA enrichment
  48. 2026-08-15 01:30 UTCEPSS rescore
  49. 2026-08-14 21:22 UTCVendor advisory
  50. 2026-08-14 21:22 UTCGHSA enrichment
  51. 2026-08-14 10:16 UTCVendor advisory
  52. 2026-08-14 10:16 UTCGHSA enrichment
  53. 2026-08-13 23:09 UTCEG score recompute
  54. 2026-08-13 23:09 UTCVendor advisory
  55. 2026-08-13 23:09 UTCGHSA enrichment
  56. 2026-08-13 22:00 UTCEPSS rescore
  57. 2026-08-13 12:00 UTCVendor advisory
  58. 2026-08-13 12:00 UTCGHSA enrichment
  59. 2026-08-13 00:53 UTCEG score recompute
  60. 2026-08-13 00:53 UTCVendor advisory
  61. 2026-08-13 00:53 UTCGHSA enrichment
  62. 2026-08-12 13:51 UTCEPSS rescore
  63. 2026-08-12 13:47 UTCVendor advisory
  64. 2026-08-12 13:47 UTCGHSA enrichment
  65. 2026-08-12 02:40 UTCVendor advisory
  66. 2026-08-12 02:40 UTCGHSA enrichment
  67. 2026-08-11 15:33 UTCEG score recompute
  68. 2026-08-11 15:33 UTCVendor advisory
  69. 2026-08-11 15:33 UTCGHSA enrichment
  70. 2026-08-11 04:25 UTCEG score recompute
  71. 2026-08-11 04:25 UTCVendor advisory
  72. 2026-08-11 04:25 UTCGHSA enrichment
  73. 2026-08-11 00:00 UTCEPSS rescore
  74. 2026-08-10 17:19 UTCVendor advisory
  75. 2026-08-10 17:19 UTCGHSA enrichment

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 August 5, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 97.3% of all scored CVEs.
What is the CVSS score of CVE-2026-53057?
CVE-2026-53057 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
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

See which npm, PyPI, Go, and Maven packages are affected by 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