CVE-2026-53293

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM 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
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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(medium)
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 PROB
0%
EPSS %ILE
2%
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.

Patch Availability(22)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-24ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-24ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-24ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-24ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-24ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-24ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-24ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-24ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-24ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-24ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-24ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-24ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-24ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1056.57~22.04.2) @ jammy2026-08-24ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-24ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-24ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-24ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-24ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1059.62~22.04.1) @ jammy2026-08-24ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-24ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-24ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-24ubuntu

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (137 versions)7.0.10-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(22)

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 19× in last 7d / 90× 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 154 total refreshes for this CVE.

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

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% probability of exploitation in the next 30 days, which ranks it in the top 97.6% of all scored CVEs.
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

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