Deadlock Vulnerability in Linux Kernel: AMDGPU DebugFS Files

linux Updated 02 Oct 2025

Summary

17/05/2024
N/A
Yes i
Unrated
Not published

DEBIAN-CVE-2024-35795: In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix deadlock while reading mqd from debugfs An errant disk backup on my desktop got into debugfs and triggered the following deadlock scenar... Affects linux versions < 6.7.12-1. Fixed in 6.7.12-1. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Linux kernel is the core component of many operating systems, providing essential services for hardware and software interactions. The 'linux' package in Debian versions 13 and 14 is crucial for system stability and performance. This package includes drivers and subsystems for various hardware components, including graphics processing units (GPUs). The vulnerability in question affects the AMDGPU driver, which is responsible for managing AMD graphics cards, particularly in scenarios involving debug file system (debugfs) interactions.

Vulnerability Detail

In the Linux kernel, a deadlock vulnerability has been identified within the AMDGPU debugfs files. This issue arises when an errant disk backup interacts with debugfs, leading to a circular locking dependency. The deadlock scenario occurs when a task attempts to acquire a lock that is already held by another task, which in turn is waiting for the first lock to be released. This can result in system instability, potentially causing the machine to hard-reset. The vulnerability was introduced in earlier versions and has been fixed in version 6.7.12-1.

How To Fix

Minimum fixed version

6.7.12-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade linux

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

Currently, there are no specific workarounds mentioned for this vulnerability. It is recommended to apply the patch as soon as it is available to mitigate the risks associated with the deadlock scenario.

Conclusion

The deadlock vulnerability in the Linux kernel's AMDGPU debugfs files poses a significant risk to system stability. Users are urged to update their 'linux' package to version 6.7.12-1 or later to mitigate this issue. Regular monitoring and updates are essential for maintaining system security.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

The deadlock vulnerability involves a circular locking dependency in the AMDGPU debugfs files, which can lead to system instability.

You can use Vulert, which monitors open-source vulnerabilities in your software. By checking your manifest file with Vulert's playground, you can identify if your application is affected.

Failure to address this vulnerability may result in system crashes or hard resets, affecting system reliability and performance.

Yes, the vulnerability has been fixed in version 6.7.12-1 of the Linux package.

It is advisable to regularly check for updates to your packages, ideally on a weekly basis, to ensure you have the latest security patches.

Related vulnerabilities

Recent vulnerabilities recorded for linux.

How To Fix

Minimum fixed version

6.7.12-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade linux

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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