Vulnerability in thermal/drivers/broadcom package: Potential NULL dereference in sr_thermal_probe
Summary
GSD-2022-1003362: thermal/drivers/broadcom: Fix potential NULL dereference in sr_thermal_probe. Affects Kernel versions >= 250e211057c7237dc75634b1372a1a3bd58dcd96, < ef1235c6514a58f274246cf4a2d5f4e40af539ce. 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 thermal/drivers/broadcom package is a component of the Linux Kernel. It provides support for thermal management on Broadcom devices. The sr_thermal_probe function within this package is responsible for probing the thermal sensors on these devices. These sensors play a crucial role in monitoring and controlling the temperature of the hardware. However, a potential vulnerability has been identified in the sr_thermal_probe function, which could lead to a NULL dereference.
Vulnerability Detail
The vulnerability arises from a potential NULL dereference in the sr_thermal_probe function of the thermal/drivers/broadcom package. If this function encounters a NULL pointer, it may result in a system crash or other unpredictable behavior. An attacker could potentially exploit this vulnerability to cause a denial-of-service (DoS) attack or gain unauthorized access to sensitive information. The vulnerability was introduced in version v5.1 of the Linux Kernel and has been fixed in version v5.15.46.
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
No specific workaround has been mentioned for this vulnerability.
Conclusion
In conclusion, the thermal/drivers/broadcom package in the Linux Kernel is vulnerable to a potential NULL dereference in the sr_thermal_probe function. This vulnerability can lead to system crashes, DoS attacks, or unauthorized access to sensitive information. It is crucial to update the Kernel to version v5.15.46 or later to mitigate this vulnerability. For further assistance or support in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability could potentially lead to a system crash or other unpredictable behavior. It may also be exploited by attackers to cause a denial-of-service (DoS) attack or gain unauthorized access to sensitive information.
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 and the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.
Yes, a patch has been released in version v5.15.46 of the Linux Kernel. It is recommended to update to this version or later to fix the vulnerability.
Unfortunately, no specific temporary measures have been provided for this vulnerability. It is recommended to update the Kernel as soon as possible to ensure the security of your system.
You can find more information about this vulnerability in the Open Source Vulnerability Database (OSVDB) entry: https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1003xxx/GSD-2022-1003362.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
