Unexported __init-annotated tick_nohz_full_setup() in Kernel
Summary
GSD-2022-1004241: tick/nohz: unexport __init-annotated tick_nohz_full_setup(). Affects Kernel versions >= ae9e557b5be2e285f48ee945d9c8faf75d4f6a66, < ea32b27e2f8c58c92bff5ecba7fcf64b97707089. 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 Kernel is a fundamental component of the Linux operating system that manages system resources and facilitates communication between hardware and software. It provides essential functionalities for the proper functioning of the system. The tick/nohz subsystem in the Kernel handles the system timer and the management of idle CPUs. One of the functions within this subsystem, tick_nohz_full_setup(), has been unexported, which means it is no longer accessible outside of the Kernel. This vulnerability affects the Linux Kernel versions 5.5 to 5.18.8.
Vulnerability Detail
The unexported __init-annotated tick_nohz_full_setup() function in the Kernel can potentially lead to security vulnerabilities. While the exact impact and attack plausibility have not been proven, it is crucial to address this issue to ensure the overall security and stability of the system. The vulnerability was introduced in Kernel version 5.5 and fixed in version 5.18.9.
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 this vulnerability has been fixed in Kernel version 5.18.9, applying the update is the recommended solution. However, if updating the Kernel is not feasible, an alternative workaround is not available.
Conclusion
The unexported __init-annotated tick_nohz_full_setup() function in the Kernel poses a potential security vulnerability. To mitigate this issue, it is crucial to update the Linux Kernel to version 5.18.9 or later. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The exact impact of this vulnerability is not yet proven. However, it is essential to address it to maintain the security and stability of the system.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your manifest file, such as package-lock.json, and Vulert will provide real-time alerts for open-source vulnerabilities.
No, there is no workaround available for this vulnerability. It is recommended to update the Linux Kernel to version 5.18.9 or later.
The official Linux Kernel repository can be found at https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/.
This vulnerability affects Linux Kernel versions 5.5 to 5.18.8.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.