NULL pointer dereference in amdgpu_dm_connector_add_common_modes() in Kernel

Kernel Updated 02 Oct 2025

Summary

24/04/2022
N/A
No i
Unrated
Not published

GSD-2022-1001551: drm/amd/display: Fix a NULL pointer dereference in amdgpu_dm_connector_add_common_modes(). Affects Kernel versions >= e7b07ceef2a650e5ed8ca37997689e086c680daf, < f4eaa999fec78dec2a9c2d797438e05cbffb125b. 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 Kernel is a fundamental component of the Linux operating system, responsible for managing system resources and providing an interface between hardware and software. It is crucial for the proper functioning of the system. The amdgpu_dm_connector_add_common_modes() function is part of the display subsystem in the Kernel, specifically in the drm/amd/display module. This function is responsible for adding common display modes to an AMD GPU connector. A NULL pointer dereference vulnerability has been identified in this function.

Vulnerability Detail

The NULL pointer dereference vulnerability in amdgpu_dm_connector_add_common_modes() occurs when a NULL pointer is accessed, leading to a system crash or potential privilege escalation. An attacker could exploit this vulnerability by sending specially crafted input to a vulnerable system, causing the function to dereference a NULL pointer. This could result in a denial of service (system crash) or potentially allow an attacker to execute arbitrary code with elevated privileges. The vulnerability was introduced in version v4.15 of the Linux Kernel and has been fixed in version v5.16.19.

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

If updating the Kernel is not immediately feasible, a possible workaround is to disable the affected functionality. This can be achieved by blacklisting the amdgpu module or preventing the loading of the module at system startup. However, this workaround may result in the loss of display capabilities for AMD GPUs.

Conclusion

The NULL pointer dereference vulnerability in amdgpu_dm_connector_add_common_modes() in the Kernel can lead to system crashes or potential privilege escalation. It is crucial to update the Linux Kernel to version v5.16.19 or later to mitigate this vulnerability. If immediate updating is not possible, a temporary workaround is available by disabling the affected functionality. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can lead to a system crash (denial of service) or potential privilege escalation, allowing an attacker to execute arbitrary code with elevated privileges.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will analyze the dependencies and alert you if any vulnerabilities are found.

Yes, the vulnerability has been fixed in version v5.16.19 of the Linux Kernel. It is recommended to update to this version or a later one to mitigate the risk.

A temporary workaround is to disable the affected functionality by blacklisting the amdgpu module or preventing its loading at system startup. However, this may result in the loss of display capabilities for AMD GPUs.

You can find more information about this vulnerability in the GSD-2022-1001551 entry of the GSD Database maintained by the Cloud Security Alliance. The entry provides details about the vulnerability, its impact, and the fix.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

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