Critical Dereference Vulnerability in Linux Kernel's DRM Subsystem

linux Updated 02 Oct 2025

Summary

08/01/2025
N/A
No i
Medium
5.5

CVE-2024-56776: In the Linux kernel, the following vulnerability has been resolved: drm/sti: avoid potential dereference of error pointers The return value of drm_atomic_get_crtc_state() needs to be checked. 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 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 a core component of many operating systems, providing essential services for hardware and software interaction. It supports a wide range of functionalities, including device drivers, file systems, and network protocols. The Direct Rendering Manager (DRM) subsystem is responsible for managing graphics processing units (GPUs) and rendering graphics efficiently. This vulnerability specifically affects the DRM subsystem, where improper handling of error pointers can lead to serious security issues.

Vulnerability Detail

In the Linux kernel, a vulnerability has been identified in the Direct Rendering Manager (DRM) subsystem, specifically in the function drm_atomic_get_crtc_state(). This function fails to adequately check the return value, which can lead to the dereferencing of error pointers. If an error occurs during the state retrieval, the system may attempt to use an invalid pointer, potentially causing a crash or allowing an attacker to exploit the situation to execute arbitrary code. This vulnerability poses a significant risk, especially in environments where graphics rendering is critical.

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 provided for this vulnerability. The best course of action is to apply the available patches as soon as they are released.

Conclusion

The vulnerability CVE-2024-56776 in the Linux kernel's DRM subsystem poses a significant risk due to improper error handling. Users are strongly advised to update their systems to the latest patched versions to mitigate this risk. Regular monitoring and vulnerability management practices, such as using tools like Vulert, can help maintain system security.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

CVE-2024-56776 is a vulnerability in the Linux kernel's DRM subsystem that can lead to dereferencing error pointers, potentially causing system crashes or exploitation.

You can use Vulert to monitor and alert for open-source vulnerabilities. By uploading your manifest file like package-lock.json, you can check if your application is affected by CVE-2024-56776.

The CVSS score for this vulnerability is 5.5, indicating a moderate level of severity.

Yes, patches are available for Debian 12 and Debian 13. Ensure you update to the specified versions to mitigate the risk.

While there are no specific workarounds, it is crucial to prioritize updating your system to the patched versions as soon as possible to protect against potential exploitation.

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