CVE-2023-53753

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-12-08. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.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: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

drm/amd/display: fix mapping to non-allocated address

[Why] There is an issue mapping non-allocated location of memory. It would allocate gpio registers from an array out of bounds.

[How] Patch correct numbers of bounds for using.

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

Published

December 8, 2025

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

drm/amd/display: fix mapping to non-allocated address - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9190d4a263264eabf715f5fc1827da45e3fdc247
generic

drm/amd/display: fix mapping to non-allocated address - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/24aaf6603600d6d1159973c809ea2737664b28c4
generic

drm/amd/display: fix mapping to non-allocated address - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8ce8a443ddd9002861a4ee8a7e33a0c02717422f

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:4.18.0-513.5.1.el8_92023-11-14redhat
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 6.1.16osv

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 (498 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.20-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.1.20-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.1.20-1

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2023-53753?
CVE-2023-53753 is a high vulnerability published on December 8, 2025. In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: fix mapping to non-allocated address [Why] There is an issue mapping non-allocated location of memory. It would allocate gpio registers from an array out of bounds. [How] Patch correct numbers of bounds for using.
When was CVE-2023-53753 disclosed?
CVE-2023-53753 was first published in the National Vulnerability Database on December 8, 2025, 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-2023-53753 actively exploited?
CVE-2023-53753 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 96.2% of all scored CVEs.
What is the CVSS score of CVE-2023-53753?
CVE-2023-53753 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2023-53753?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-53753, 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-2023-53753

Explore →

Is Your Infrastructure Affected by CVE-2023-53753?

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