Vulnerability in drm/tegra: sor: Do not leak runtime PM reference
Summary
GSD-2021-1000910: drm/tegra: sor: Do not leak runtime PM reference. Affects Kernel versions < e4c3f7a6a3b241aab8aaebe50b7dbf11b5d8a5ee. 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 drm/tegra package is a component of the Linux Kernel, which is responsible for managing the display subsystem on NVIDIA Tegra SoCs. It provides the necessary drivers and functionality for graphics rendering and display output. The 'sor' module within drm/tegra handles the runtime power management (PM) for the display subsystem. Runtime PM allows the system to dynamically power on or off specific components to conserve energy. However, a vulnerability has been discovered in the sor module that can lead to a runtime PM reference leak.
Vulnerability Detail
The vulnerability in the drm/tegra: sor module results in a runtime PM reference leak. This leak occurs when the module fails to release the reference to the runtime PM, leading to a resource leak. An attacker could potentially exploit this vulnerability to exhaust system resources, resulting in a denial of service (DoS) condition. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability has been fixed in Linux Kernel version v5.4.127 by commit e4c3f7a6a3b241aab8aaebe50b7dbf11b5d8a5ee.
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 drm/tegra: sor module can lead to a runtime PM reference leak, potentially resulting in a denial of service (DoS) condition. It is crucial to update the Linux Kernel to version v5.4.127 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven. However, it could potentially lead to a denial of service (DoS) condition by exhausting system resources.
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 and alert you in real-time if any open-source vulnerabilities, including this one, are found.
Yes, the vulnerability has been fixed in Linux Kernel version v5.4.127 by commit e4c3f7a6a3b241aab8aaebe50b7dbf11b5d8a5ee. It is recommended to update to this version or later to mitigate the vulnerability.
There are no specific temporary measures mentioned for this vulnerability. It is recommended to update the kernel as soon as possible to ensure the system is protected.
You can find more information about this vulnerability in the GSD-2021-1000910.json file available in the GSD database (https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1000xxx/GSD-2021-1000910.json).
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
