Skip to content
Fencer Vulns
high 7.8

CVE-2023-53753 json

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

published 2025-12-08 11 mo ago modified 2026-10-15 24 d ago also EUVD-2023-60075

cvss
7.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 4%
public exploits
0
none known

Summary

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.

Patch / fix

  • Linux Linux 6.1.16, 6.2.3, 6.3
  • linux Debian 14, Debian 13, Debian 12 6.1.20-1

debian advisories DEBIAN-CVE-2023-53753

  • kernel RHEL 8 4.18.0-513.5.1.el8_9
  • perf RHEL 8 4.18.0-513.5.1.el8_9
  • bpftool RHEL 8 4.18.0-513.5.1.el8_9
  • kernel-core RHEL 8 4.18.0-513.5.1.el8_9
  • kernel-tools RHEL 8 4.18.0-513.5.1.el8_9
  • python3-perf RHEL 8 4.18.0-513.5.1.el8_9
  • kernel-modules RHEL 8 4.18.0-513.5.1.el8_9
  • kernel-zfcpdump RHEL 8 4.18.0-513.5.1.el8_9

red hat advisories RHSA-2023:7077RHSA-2023:6583

  • kernel-64kb SLES 15 SP5-LTSS, SLE High Performance Computing 15 SP5-LTSS, SLE High Performance Computing 15 SP5-ESPOS 5.14.21-150500.55.133.1
  • kernel-syms SLES for SAP 15 SP5, SLES 15 SP5-LTSS, SLE High Performance Computing 15 SP5-LTSS +1 more 5.14.21-150500.55.133.1
  • kernel-source SLES for SAP 15 SP5, SLES 15 SP5-LTSS, SLE Micro 5.5 +2 more 5.14.21-150500.55.133.1
  • kernel-default SLES for SAP 15 SP5, SLES 15 SP5-LTSS, SLE Micro 5.5 +3 more 5.14.21-150500.55.133.1
  • kernel-obs-build SLES for SAP 15 SP5, SLES 15 SP5-LTSS, SLE High Performance Computing 15 SP5-LTSS +1 more 5.14.21-150500.55.133.1
  • kernel-default-base SLES for SAP 15 SP5, SLES 15 SP5-LTSS, SLE Micro 5.5 +2 more 5.14.21-150500.55.133.1.150500.6.65.1
  • kernel-rt SLE Micro 5.5 5.14.21-150500.13.118.1
  • kernel-source-rt SLE Micro 5.5 5.14.21-150500.13.118.1

suse advisories SUSE-SU-2026:0317-1SUSE-SU-2026:0263-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-53753 updated cvss 5.5

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

  • Red Hat Enterprise Linux 8 kernel-rt, kernel-rt-kvm, kernel-rt-core, kernel-rt-modules, kernel-rt-debug-kvm, kernel-rt-debug-core, +6 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more
    affected: no fix available “Fix deferred”
  • Red Hat CodeReady Linux Builder (v. 8) kernel-debuginfo-common-x86_64 4.18.0-513.5.1.el8_9, kernel-debuginfo-common-aarch64 4.18.0-513.5.1.el8_9, kernel-debuginfo-common-ppc64le 4.18.0-513.5.1.el8_9 Red Hat Enterprise Linux BaseOS (v. 8) perf 4.18.0-513.5.1.el8_9, kernel 4.18.0-513.5.1.el8_9, bpftool 4.18.0-513.5.1.el8_9, kernel-core 4.18.0-513.5.1.el8_9, kernel-tools 4.18.0-513.5.1.el8_9, python3-perf 4.18.0-513.5.1.el8_9, +15 more
    fixed: vendor fix RHSA-2023:7077
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 10 kernel
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
24 d ago

Exploit prediction

0.15% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Linux Linux

Classification

Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.