Vulnerability in drm/msm Package: Freeing Unrequested IRQ
Summary
GSD-2022-1003358: drm/msm: don't free the IRQ if it was not requested. Affects Kernel versions >= f026e431cf861197dc03217d1920b38b80b31dd9, < beb81c13d020ceb7f8693e65464162e5f249218e. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The drm/msm package is a component of the Linux Kernel that provides support for graphics rendering on Qualcomm Adreno GPUs. It is responsible for managing the display and rendering capabilities of these GPUs. The package includes various drivers and modules that enable communication between the GPU and the rest of the system. One critical aspect of this package is the handling of interrupts, which are used to signal events that require immediate attention from the GPU driver.
The vulnerability in question pertains to the improper handling of interrupts that were not requested by the driver. When an interrupt is received but was not explicitly requested, the driver attempts to free the corresponding interrupt resource. However, this action can lead to memory corruption or other undefined behavior, potentially resulting in a system crash or unauthorized access to sensitive information.
Vulnerability Detail
The vulnerability arises from a flaw in the drm/msm package's interrupt handling mechanism. When an interrupt is received but was not requested by the driver, the package erroneously attempts to free the interrupt resource. This can lead to memory corruption or other undefined behavior, posing a significant security risk. An attacker could potentially exploit this vulnerability to crash the system or gain unauthorized access to sensitive information.
The vulnerability was introduced in version v5.15 of the Linux Kernel by commit f026e431cf861197dc03217d1920b38b80b31dd9. It was fixed in version v5.15.46 by commit beb81c13d020ceb7f8693e65464162e5f249218e.
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
As a workaround, users can disable the affected functionality by modifying the configuration of the Linux Kernel. However, this may result in the loss of certain graphics rendering capabilities or other related features. It is strongly advised to apply the official fix by updating the Linux Kernel to the recommended version.
Conclusion
The vulnerability in the drm/msm package's interrupt handling mechanism can lead to memory corruption, system crashes, or unauthorized access to sensitive information. It is crucial to update the Linux Kernel to version v5.15.46 or later to address this vulnerability. Users can also utilize the Vulert Playground at https://vulert.com/scanner to check if their systems are affected by this vulnerability. For additional support and assistance, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially lead to system crashes or unauthorized access to sensitive information. It poses a significant security risk and should be addressed promptly.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file, and Vulert will analyze it for any open-source vulnerabilities, including this one.
At the time of this report, no known exploits for this vulnerability have been identified. However, it is crucial to apply the recommended fix to mitigate any potential risks.
While it is technically possible to manually patch the affected code, it is strongly recommended to update the Linux Kernel to the latest stable version. Manually patching the code can be error-prone and may introduce other issues or conflicts.
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 in addressing this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
