Kernel Vulnerability in Linux: AMDGPU TTM_BO Calltrace Warning Fix

linux Updated 02 Oct 2025

Summary

02/05/2025
N/A
No i
Unrated
Not published

CVE-2023-53074: In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix ttm_bo calltrace warning in psp_hw_fini The call trace occurs when the amdgpu is removed after the mode1 reset. Affects linux versions 5.10.103-1 – 6.9.9-1. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The Linux kernel is a core component of many operating systems, providing essential services for hardware and software interaction. The AMDGPU driver is responsible for managing AMD graphics cards, enabling high-performance graphics rendering. This vulnerability specifically affects the AMDGPU driver, leading to potential instability when the driver is unloaded after a mode1 reset.

Vulnerability Detail

In the Linux kernel, specifically within the AMDGPU driver, a vulnerability has been identified that causes a call trace warning during the unloading of the driver after a mode1 reset. This issue arises due to unnecessary reinitialization of the firmware buffer, leading to an increase in the buffer's pin count. If not addressed, this could result in system instability or crashes when the AMDGPU driver is removed, particularly after transitioning from suspend to resume states.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

Currently, there are no specific workarounds mentioned for this vulnerability. It is advisable to apply the patch as soon as it is available to mitigate any potential risks.

Conclusion

The CVE-2023-53074 vulnerability in the Linux kernel's AMDGPU driver poses a risk of system instability during driver unloading. It is essential to update to the patched version to ensure system integrity and performance.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

CVE-2023-53074 is a vulnerability in the Linux kernel's AMDGPU driver that leads to call trace warnings when the driver is unloaded after a mode1 reset.

This vulnerability can cause system instability or crashes when the AMDGPU driver is removed, especially after the system resumes from a suspended state.

Yes, a patch is available in the form of Linux package version 6.1.25-1 or later. It is recommended to update your system to this version.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application against this vulnerability using the Vulert playground at Vulert Scanner.

While there are no specific workarounds provided, it is crucial to monitor your system for any unusual behavior and apply the patch as soon as possible.

Related vulnerabilities

Recent vulnerabilities recorded for linux.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback