LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53545: drm/amdgpu: unmap and remove csa_va properly

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: unmap and remove csa_va properly Root PD BO should be reserved before unmap and remove a bo_va from VM otherwise lockdep will complain. v2: check fpriv->csa_va is not NULL instead of amdgpu_mcbp (christian) [14616.936827] WARNING: CPU: 6 PID: 1711 at drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c:1762 amdgpu_vm_bo_del+0x399/0x3f0 [amdgpu] [14616.937096] Call Trace: [14616.937097] <TASK> [14616.937102] amdgpu_driver_postclose_kms+0x249/0x2f0 [amdgpu] [14616.937187] drm_file_free+0x1d6/0x300 [drm] [14616.937207] drm_close_helper.isra.0+0x62/0x70 [drm] [14616.937220] drm_release+0x5e/0x100 [drm] [14616.937234] __fput+0x9f/0x280 [14616.937239] ____fput+0xe/0x20 [14616.937241] task_work_run+0x61/0x90 [14616.937246] exit_to_user_mode_prepare+0x215/0x220 [14616.937251] syscall_exit_to_user_mode+0x2a/0x60 [14616.937254] do_syscall_64+0x48/0x90 [14616.937257] entry_SYSCALL_64_after_hwframe+0x63/0xcd

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE affects the Linux kernel AMDGPU driver. The disclosed issue is an improper cleanup sequence for an AMD GPU virtual-memory object when a graphics file handle closes. Public sources show a kernel fix, but they do not describe data theft, remote access, privilege escalation, or service-impact severity.

Executive priority

Track and patch through normal kernel maintenance unless your fleet relies heavily on AMDGPU workloads. There is no source-backed evidence of exploitation or severe impact, but kernel driver flaws deserve timely remediation because impact can be hard to assess from brief CVE records.

Technical view

The flaw is in drm/amdgpu cleanup of csa_va. The root page-directory buffer object should be reserved before unmapping and removing a BO VA from a VM. The provided trace shows a lockdep warning in amdgpu_vm_bo_del during amdgpu_driver_postclose_kms. Stable kernel commits resolve the ordering and null-check behavior.

Likely exposure

Exposure appears limited to Linux systems using the AMDGPU kernel driver on affected kernel builds. The source bundle lists Linux as affected across several kernel version entries, but does not provide CPEs, distribution packages, or hardware-specific scope beyond amdgpu.

Exploitation context

The source bundle does not show active exploitation, and KEV is false. It also does not provide exploitability details. Treat this as a kernel-driver correctness issue with unclear security impact until vendor or distribution advisories provide severity and attack requirements.

Researcher notes

Public evidence is sparse: no CVSS, CWE, CPE, exploit status, or concrete impact statement is provided. The strongest facts are the amdgpu call trace, the cleanup-order description, KEV false, and four stable commit references. Avoid assuming privilege escalation or denial of service without additional vendor analysis.

Mitigation direction

  • Update to a vendor-supported kernel containing the referenced stable fixes.
  • Check distribution advisories for fixed package versions and reboot requirements.
  • Prioritize systems with AMD GPUs and loaded amdgpu driver exposure.
  • If no vendor fix is available, monitor vendor guidance before applying custom kernels.

Validation and detection

  • Inventory Linux kernel versions on AMD GPU systems.
  • Confirm whether the running kernel includes one of the referenced stable commits.
  • Review vendor changelogs for CVE-2023-53545 or the amdgpu csa_va fix.
  • Check kernel logs for related amdgpu_vm_bo_del or lockdep warnings.
Prepared
Confidence
medium
Sources
6

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-53545 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21, d38ceaf99ed015f2a0b9af3499791bd3a3daae21unaffected
LinuxLinux4.2, 0, 5.15.209, 6.1.167, 6.4.12, 6.5affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.