CVE-2023-53077: drm/amd/display: fix shift-out-of-bounds in CalculateVMAndRowBytes
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: fix shift-out-of-bounds in CalculateVMAndRowBytes
[WHY]
When PTEBufferSizeInRequests is zero, UBSAN reports the following
warning because dml_log2 returns an unexpected negative value:
shift exponent 4294966273 is too large for 32-bit type 'int'
[HOW]
In the case PTEBufferSizeInRequests is zero, skip the dml_log2() and
assign the result directly.
Security readout for executives and security teams
Plain-English summary
CVE-2023-53077 is a Linux kernel flaw in the AMD display driver code. A zero-size value can trigger an invalid bit shift reported by UBSAN. Public sources do not provide CVSS, demonstrated impact, or active exploitation evidence. Treat this as a kernel maintenance issue, prioritized for systems using affected AMD display functionality.
Executive priority
Schedule remediation through normal kernel patch cycles, with higher priority for Linux desktops, workstations, or GPU-enabled systems using AMD display. Escalate only if your vendor later publishes higher severity, exploitability details, or active exploitation evidence.
Technical view
The issue is in drm/amd/display CalculateVMAndRowBytes. When PTEBufferSizeInRequests is zero, dml_log2 can return an unexpected negative value, producing a shift exponent outside valid bounds. The upstream fix skips dml_log2 for zero and assigns the result directly. Linux stable commit references are provided.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions with the drm/amd/display component in use. The source bundle lists Linux kernel as affected and provides stable fix commits. It does not establish exposure for every Linux deployment or name distribution-specific packages.
Exploitation context
No cited source states active exploitation, and this CVE is not marked in KEV. The public description shows a UBSAN-detected shift-out-of-bounds condition, but does not describe attacker control, privilege requirements, or practical impact. Exploitability remains unclear from the provided evidence.
Researcher notes
The record lacks CVSS, CWE, and concrete impact details. Analysis should focus on code reachability for PTEBufferSizeInRequests equal to zero in AMD display paths and whether the undefined behavior can cause denial of service or other consequences in real configurations.
Mitigation direction
Apply a vendor kernel update that includes the referenced stable Linux fixes.
If using distro kernels, follow the distribution security advisory for CVE-2023-53077.
Prioritize systems using AMD display functionality or graphics workloads.
If no vendor package is available, monitor kernel stable guidance before backporting.
Validation and detection
Inventory Linux kernel versions across endpoints and graphics-capable hosts.
Identify systems using AMDGPU or drm/amd/display functionality.
Check whether the referenced stable fix commit is present in the running kernel source/package.
Confirm patched kernel deployment after reboot using standard asset tooling.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2023-53077 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
6Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 2, 2025, 15:55 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.