Deadlock on DSI device attach error in Kernel
Summary
GSD-2022-1000490: drm/vc4: Fix deadlock on DSI device attach error. Affects Kernel versions < dddd832f35096fbc5004e3a7e58fb4d2cefb8deb. 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 fundamental component of the Linux operating system that acts as a bridge between the hardware and software layers. It provides essential services, such as device drivers, memory management, and process scheduling. The vulnerability in question affects the Kernel's drm/vc4 module, which is responsible for managing the display subsystem on Broadcom VideoCore IV GPUs. This vulnerability specifically relates to a deadlock that occurs when encountering a DSI (Display Serial Interface) device attach error.
Vulnerability Detail
The deadlock on DSI device attach error vulnerability in the Kernel's drm/vc4 module can lead to system instability and potential denial-of-service (DoS) conditions. When a DSI device attach error occurs, the system can become deadlocked, causing it to freeze or become unresponsive. This vulnerability can be exploited by an attacker with local access to the affected system to disrupt its normal operation. The issue has been addressed in Linux Kernel version v5.16.10 by commit dddd832f35096fbc5004e3a7e58fb4d2cefb8deb.
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 deadlock on DSI device attach error vulnerability in the Kernel's drm/vc4 module can lead to system instability and potential denial-of-service (DoS) conditions. It is crucial to update the Linux Kernel to version v5.16.10 or later to mitigate this vulnerability. Users can obtain the updated Kernel source code from the official Linux Kernel repository or wait for their Linux distribution to provide an updated package. For further support and assistance, contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to system instability and potential denial-of-service (DoS) conditions. An attacker with local access to the affected system can exploit this vulnerability to disrupt its normal operation.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) to the playground, and it will analyze the dependencies and alert you if any vulnerabilities, including this one, are found.
At the time of this report, there are no known public exploits targeting this specific vulnerability. However, it is always recommended to apply security patches promptly to mitigate any potential risks.
No, this vulnerability requires local access to the affected system to be exploited.
For further support and assistance with vulnerability remediation, you can reach out to info@devnack.com. Our team of experts will be happy to assist you.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
