Fix 'BUG: Invalid wait context' in watchdog: rzg2l_wdt
Summary
GSD-2022-1002986: watchdog: rzg2l_wdt: Fix 'BUG: Invalid wait context'. Affects Kernel versions >= 2cbc5cd0b55fa2310cc557c77b0665f5e00272de, < 6505541e5298cea2b79da68ee626f583f8e18784. 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 watchdog package is responsible for monitoring the health and functionality of a system. It includes a driver called rzg2l_wdt, which is used for Renesas RZ/G2L SoCs. This driver provides a watchdog timer that can be used to detect and recover from system failures. However, a vulnerability has been discovered in the rzg2l_wdt driver that can lead to a 'BUG: Invalid wait context' error.
Vulnerability Detail
The 'BUG: Invalid wait context' vulnerability in the rzg2l_wdt driver can be triggered when certain wait contexts are used incorrectly. This can result in a kernel panic or other system instability, potentially leading to a denial of service or privilege escalation. The vulnerability was introduced in Linux Kernel version v5.17 by commit 2cbc5cd0b55fa2310cc557c77b0665f5e00272de and is fixed in version v5.17.15 by commit 6505541e5298cea2b79da68ee626f583f8e18784.
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 →
Conclusion
The 'BUG: Invalid wait context' vulnerability in the watchdog: rzg2l_wdt driver can lead to system instability and potential denial of service or privilege escalation. It is recommended to update the Linux Kernel to version v5.17.15 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a kernel panic or other system instability, potentially resulting in a denial of service or privilege escalation.
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 it will provide real-time alerts for open-source vulnerabilities.
At the time of this report, there are no known exploits for this vulnerability. However, it is still important to apply the fix to prevent potential attacks.
No specific workaround has been provided for this vulnerability. It is recommended to update to the fixed version of the Linux Kernel.
You can find more information about this vulnerability in the vulnerability database maintained by the Cloud Security Alliance: https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1002xxx/GSD-2022-1002986.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
