CVE-2026-53374

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
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:

drm/amdgpu: zero-initialize GART table on allocation

GART TLB is flushed after unmapping but not after mapping. Since amdgpu_bo_create_kernel() does not zero-initialize the buffer, when a single PTE is written the TLB may speculatively load other uninitialized entries from the same cacheline. Those garbage entries can appear valid, and a subsequent write to another PTE in the same cacheline may cause the GPU to use a stale garbage PTE from the TLB.

Fix this by calling memset_io() to zero-initialize the GART table with gart_pte_flags immediately after allocation.

Using AMDGPU_GEM_CREATE_VRAM_CLEARED, SDMA-based clear will not work since SDMA needs GART to be initialized to work.

(cherry picked from commit d9af8263b82b6eaa60c5718e0c6631c5037e4b24)

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

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated Jul 20, 2026
No patch confirmed yet.
generic

drm/amdgpu: zero-initialize GART table on allocation - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdgpu: zero-initialize GART table on allocation - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdgpu: zero-initialize GART table on allocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/91fbb5e635c8fb1b49e15c19da06480089ef719f
generic

drm/amdgpu: zero-initialize GART table on allocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8ae8b9e74bab94aab1d79f1688129bcc61c8b29a
generic

drm/amdgpu: zero-initialize GART table on allocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/791941be5da125d9a1b228582bfdc300c05d05b3
generic

drm/amdgpu: zero-initialize GART table on allocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/40df11255d71b02e20e70579f1b12b687e396e26

Vendor Advisories for CVE-2026-53374(3)

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

Patch Availability(22)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-30ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-30ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-30ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-30ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-30ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-30ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1061.64~22.04.1) @ jammy2026-08-30ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-30ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-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
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-30ubuntu
redhatkernel-0:5.14.0-687.41.1.el9_82026-08-20redhat
redhatkernel-0:6.12.0-211.49.1.el10_22026-08-20redhat
redhatkernel-rt-0:4.18.0-553.156.1.rt7.497.el8_102026-08-17redhat
redhatkernel-0:4.18.0-553.156.1.el8_102026-08-17redhat

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.90-1~bpo12+1 (23 versions)6.12.90-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (135 versions)7.0.9-1—

Additional Vendor Advisories

(21)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 34× in last 7d / 164× 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 205 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53374?
CVE-2026-53374 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: zero-initialize GART table on allocation GART TLB is flushed after unmapping but not after mapping. Since amdgpubocreate_kernel() does not zero-initialize the buffer, when a single PTE is written the TLB may…
When was CVE-2026-53374 disclosed?
CVE-2026-53374 was first published in the National Vulnerability Database on July 19, 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-53374 actively exploited?
CVE-2026-53374 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.4% of all scored CVEs.
What is the CVSS score of CVE-2026-53374?
CVE-2026-53374 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53374?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53374, 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-53374

Explore →

Is Your Infrastructure Affected by CVE-2026-53374?

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

Start Free Scan →Browse All CVEs