CVE-2023-53152
BaseFortify
Publication date: 2025-09-15
Last updated on: 2025-11-24
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-772 | The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability involves a calltrace warning in the Linux kernel's amdgpu driver related to the improper freeing of buffer objects (BOs) allocated for the PSP (Platform Security Processor). Specifically, these BOs are not freed until the driver is removed, causing a call trace warning during amdgpu driver removal. Additionally, for certain GPU versions (smu v13_0_2 with xgmi support), the GPU recovery process during device removal causes hardware reset without proper resume of some IP blocks, leading to incomplete hardware finalization. The fix involves adjusting the removal control flow and moving some software operations to the appropriate finalization function.
How can this vulnerability impact me? :
This vulnerability can cause warnings and potential instability during the removal of the amdgpu driver due to resources not being freed properly. In certain GPU configurations, incomplete hardware finalization during device removal could lead to improper device reset behavior, which might affect system stability or GPU functionality during driver unload or hardware reset scenarios.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by observing the kernel logs for the specific call trace warning related to amddrm_buddy_fini when removing the amdgpu driver. You can check the kernel log messages using the command: dmesg | grep amddrm_buddy_fini. Look for call trace entries similar to those described in the vulnerability, indicating that BOs allocated for psp are not freed until removing.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the Linux kernel to a version where this vulnerability has been fixed, as the issue is resolved by changes in the amdgpu driver related to freeing BOs allocated for psp and adjusting removal control flow for smu v13_0_2. Until then, avoid removing the amdgpu driver unnecessarily to prevent the call trace warning and potential related issues.