CVE-2026-53293

MEDIUMNVD 5.55.5—
EchelonGraph scoreHIGH confidence

Score 5.5 from GitHub Security Advisory published 2026-06-26. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: 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:

drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG

There were multiple issues in that code.

First of all the order between the reset semaphore and the mm_lock was wrong (e.g. copy_to_user) was called while holding the lock.

Then we allocated memory while holding the reset semaphore which is also a pretty big bug and can deadlock.

Then we used down_read_trylock() instead of waiting for the reset to finish.

(cherry picked from commit 361b6e6b303d4b691f6c5974d3eaab67ca6dd90e)

CVSS v3
5.5
EG Score
5.5(high)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
0.9%
KEV
Not listed

Published

June 26, 2026

Last Modified

July 8, 2026

Advisory Details (5)

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

drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/61957c2e467b39b528a290016367d32a433fa846
generic

drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5c29d20470d4566d1b68df57097d642d01f8b427
generic

drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-53293(2)

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

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 56× 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-24 14:18 UTCEPSS rescore
  2. 2026-07-23 03:19 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-18 10:04 UTCEPSS rescore
  6. 2026-07-16 21:43 UTCVendor advisory
  7. 2026-07-16 21:43 UTCGHSA enrichment
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-15 20:05 UTCVendor advisory
  10. 2026-07-15 20:05 UTCGHSA enrichment
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-14 18:28 UTCVendor advisory
  14. 2026-07-14 18:28 UTCGHSA enrichment
  15. 2026-07-13 22:31 UTCEPSS rescore
  16. 2026-07-13 16:52 UTCGHSA enrichment
  17. 2026-07-13 06:13 UTCEPSS rescore
  18. 2026-07-13 06:13 UTCEPSS rescore
  19. 2026-07-12 15:16 UTCVendor advisory
  20. 2026-07-12 15:16 UTCGHSA enrichment
  21. 2026-07-12 05:46 UTCEPSS rescore
  22. 2026-07-11 13:40 UTCVendor advisory
  23. 2026-07-11 13:40 UTCGHSA enrichment
  24. 2026-07-11 08:27 UTCEPSS rescore
  25. 2026-07-11 08:27 UTCEPSS rescore
Show 31 more
  1. 2026-07-10 12:03 UTCVendor advisory
  2. 2026-07-10 12:03 UTCGHSA enrichment
  3. 2026-07-09 19:10 UTCEPSS rescore
  4. 2026-07-09 19:10 UTCEPSS rescore
  5. 2026-07-09 10:27 UTCEG score recompute▲ 5.50
  6. 2026-07-09 10:26 UTCGHSA enrichment
  7. 2026-07-08 15:16 UTCEPSS rescore
  8. 2026-07-08 15:16 UTCEPSS rescore
  9. 2026-07-08 04:32 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  10. 2026-07-07 13:46 UTCEPSS rescore
  11. 2026-07-07 13:46 UTCEPSS rescore
  12. 2026-07-06 16:27 UTCEPSS rescore
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 07:14 UTCGHSA enrichment
  15. 2026-07-06 02:23 UTCEPSS rescore
  16. 2026-07-06 02:23 UTCEPSS rescore
  17. 2026-07-05 02:31 UTCEPSS rescore
  18. 2026-07-05 02:30 UTCEPSS rescore
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-03 04:00 UTCGHSA enrichment
  22. 2026-07-01 15:07 UTCEPSS rescore
  23. 2026-06-30 23:22 UTCEPSS rescore
  24. 2026-06-30 00:49 UTCGHSA enrichment
  25. 2026-06-29 14:06 UTCEPSS rescore
  26. 2026-06-29 14:06 UTCEPSS rescore
  27. 2026-06-28 14:07 UTCEPSS rescore
  28. 2026-06-28 04:56 UTCEPSS rescore
  29. 2026-06-28 04:56 UTCEPSS rescore
  30. 2026-06-26 21:38 UTCEG score recompute
  31. 2026-06-26 21:38 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-53293?
CVE-2026-53293 is a medium vulnerability published on June 26, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix AMDGPUINFOREADMMRREG There were multiple issues in that code. First of all the order between the reset semaphore and the mm_lock was wrong (e.g. copytouser) was called while holding the lock. Then we allocated…
When was CVE-2026-53293 disclosed?
CVE-2026-53293 was first published in the National Vulnerability Database on June 26, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53293 actively exploited?
CVE-2026-53293 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53293?
CVE-2026-53293 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53293?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53293, 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-53293

Explore →

Is Your Infrastructure Affected by CVE-2026-53293?

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

Start Free Scan →Browse All CVEs