CVE-2026-53375

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/vce: Prevent partial address patches

In the case that only one of lo/hi is valid, the patching could result in a bad address written to in FW.

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/vce: Prevent partial address patches - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdgpu/vce: Prevent partial address patches - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdgpu/vce: Prevent partial address patches - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdgpu/vce: Prevent partial address patches - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/944db9cfa5373f67eb94621d4c2eee572c05fa3f
generic

drm/amdgpu/vce: Prevent partial address patches - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2d66d1f5d8c0434e9a5ad21cc6eaf3a5e32141d5
generic

drm/amdgpu/vce: Prevent partial address patches - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-53375(2)

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

Patch Availability(18)

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

All Vendor Advisories

(18)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-53375?
CVE-2026-53375 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vce: Prevent partial address patches In the case that only one of lo/hi is valid, the patching could result in a bad address written to in FW.
When was CVE-2026-53375 disclosed?
CVE-2026-53375 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-53375 actively exploited?
CVE-2026-53375 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-53375?
CVE-2026-53375 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53375?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53375, 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-53375

Explore →

Is Your Infrastructure Affected by CVE-2026-53375?

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