Vulnerability in Kernel: drm/amdgpu/cs
Summary
GSD-2022-1003838: drm/amdgpu/cs: make commands with 0 chunks illegal behaviour. Affects Kernel versions < 15c3bcc9b5349d40207e5f8d4d799b8b4b7d13b8. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The Kernel is a critical component of the Linux operating system that provides core functionalities and interfaces with hardware devices. It acts as a bridge between the hardware and software layers, enabling the execution of various tasks and managing system resources. The drm/amdgpu/cs module within the Kernel is responsible for handling command submission and execution for AMD GPUs. It allows users to send commands to the GPU for processing. However, a vulnerability has been identified in this module that allows commands with 0 chunks, which is considered illegal behavior.
Vulnerability Detail
The vulnerability in drm/amdgpu/cs module allows the submission of commands with 0 chunks, which is not intended behavior. This could potentially lead to various security issues and system instability. Attackers may exploit this vulnerability to execute arbitrary code, escalate privileges, or cause denial-of-service conditions. The impact and attack plausibility of this vulnerability have not been proven yet. It is important to note that this vulnerability has been fixed in Linux Kernel version v4.19.247 by commit 15c3bcc9b5349d40207e5f8d4d799b8b4b7d13b8.
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
There is no specific workaround mentioned for this vulnerability.
Conclusion
The vulnerability in the drm/amdgpu/cs module of the Kernel allows the submission of commands with 0 chunks, which is considered illegal behavior. This vulnerability has been fixed in Linux Kernel version v4.19.247. It is crucial to update the Kernel to the fixed version to mitigate the vulnerability. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability could range from arbitrary code execution to privilege escalation and denial-of-service conditions. However, the actual impact and attack plausibility have not been proven yet.
Yes, this vulnerability has been fixed in Linux Kernel version v4.19.247 by commit 15c3bcc9b5349d40207e5f8d4d799b8b4b7d13b8.
To update the Linux Kernel, you can follow the official update process provided by your Linux distribution or manually compile and install the updated Kernel version. Ensure compatibility with your hardware and software environment.
The vulnerability is present in Linux Kernel versions prior to v4.19.247. It is recommended to update to the fixed version to mitigate the vulnerability.
As of now, there is no known exploit for this vulnerability. However, it is important to apply the fix as soon as possible to prevent potential exploitation.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
