clk: visconti: Array Overflow Vulnerability in visconti_clk_register_gates()
Summary
GSD-2022-1001177: clk: visconti: prevent array overflow in visconti_clk_register_gates(). Affects Kernel versions >= b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa, < 2723543c1d60278d5aef1c4ad732dbad24b84a81. 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 clk package is a component of the Linux Kernel that provides clock framework functionality. It manages the clocks of various devices in the system, ensuring proper synchronization and timing. The visconti_clk_register_gates() function is responsible for registering clock gates in the visconti clock driver. Clock gates control the flow of clock signals to specific hardware components. This vulnerability affects the visconti_clk_register_gates() function in the clk package.
Vulnerability Detail
The visconti_clk_register_gates() function in the clk package is susceptible to an array overflow vulnerability. This vulnerability allows an attacker to overwrite adjacent memory locations beyond the bounds of an array, potentially leading to memory corruption, crashes, or even remote code execution. The vulnerability was introduced in version v5.17 of the Linux Kernel and was fixed in version v5.17.2.
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 known workaround for this vulnerability. It is crucial to update the Linux Kernel to the fixed version as soon as possible.
Conclusion
The clk package in the Linux Kernel is vulnerable to an array overflow issue in the visconti_clk_register_gates() function. This vulnerability can lead to memory corruption, crashes, or remote code execution. It is crucial to update the Linux Kernel to version v5.17.2 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can potentially lead to memory corruption, crashes, or remote code execution.
You can use Vulert's playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will provide real-time alerts for open-source vulnerabilities, including this one.
At the time of this report, there are no known exploits for this vulnerability. However, it is essential to apply the fix promptly to mitigate any potential risks.
It is highly recommended to update the entire Linux Kernel to the fixed version. Manually patching the vulnerability may introduce other issues or leave the system vulnerable to other security threats.
For further support on vulnerability remediation, you can reach out to info@devnack.com. They can provide guidance and assistance in addressing this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
