CVE-2023-53545
BaseFortify
Publication date: 2025-10-04
Last updated on: 2026-03-25
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 4.2 (inc) to 6.4.12 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel's AMD GPU driver (amdgpu) involves improper handling of unmapping and removing a buffer object virtual address (bo_va) from the virtual memory (VM). Specifically, the Root Page Directory Buffer Object (Root PD BO) should be reserved before unmapping and removing a bo_va; failure to do so causes lockdep (a kernel locking correctness validator) to raise warnings. The issue was fixed by ensuring proper reservation and checking that a certain pointer (fpriv->csa_va) is not NULL before proceeding.
How can this vulnerability impact me? :
The vulnerability can cause kernel warnings related to locking issues (lockdep complaints), which may lead to instability or unexpected behavior in the AMD GPU driver within the Linux kernel. This could potentially affect system stability or GPU-related operations, especially when closing or releasing GPU resources.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by checking your system logs for warning messages related to the amdgpu driver, specifically messages like: "WARNING: CPU: ... at drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c:1762 amdgpu_vm_bo_del". Use the command 'dmesg | grep amdgpu' or 'journalctl -k | grep amdgpu' to search for such warnings in kernel logs.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this vulnerability is resolved, as it relates to proper unmapping and removal of csa_va in the amdgpu driver. Until then, monitor system logs for related warnings and avoid workloads that heavily use the amdgpu driver to reduce risk.