Vulnerability in Kernel: printk Wake Waiters for Safe and NMI Contexts
Summary
GSD-2022-1003418: printk: wake waiters for safe and NMI contexts. Affects Kernel versions >= 03fc7f9c99c1e7ae2925d459e8487f1a6f199f79, < 5c7957948c58b1c1528f8821993153fb01c3bbae. 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 critical component of the Linux operating system that manages the system's resources and facilitates communication between hardware and software. It is responsible for tasks such as process management, memory management, and device drivers. The printk function in the Kernel is used for printing messages to the system log. It is commonly used for debugging and logging purposes. However, a vulnerability has been discovered in the printk function that can potentially be exploited in safe and NMI (Non-Maskable Interrupt) contexts.
Vulnerability Detail
The vulnerability in the printk function allows an attacker to wake waiters in safe and NMI contexts. This can lead to various security issues, including denial of service (DoS) attacks, privilege escalation, and information disclosure. The vulnerability was introduced in version v4.19 of the Linux Kernel and is fixed in version v5.15.46. The specific commit that addresses this vulnerability is 5c7957948c58b1c1528f8821993153fb01c3bbae. The impact and attack plausibility of this vulnerability have not been proven yet.
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 the Kernel's printk function can have serious security implications, including DoS attacks, privilege escalation, and information disclosure. It is crucial to update the Linux Kernel to version v5.15.46 or later to mitigate these risks. If you need further assistance or support in addressing this vulnerability, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can vary depending on the attacker's capabilities and the context in which it is exploited. Possible consequences include denial of service (DoS) attacks, privilege escalation, and information disclosure.
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.
As of now, there is no known exploit for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate any potential risks.
The exact details of the vulnerability and its exploitability have not been disclosed. It is recommended to update the Kernel to the latest version to ensure the system is protected against potential remote exploitation.
The recommended solution is to update the Linux Kernel to the latest version. However, if updating is not feasible, you can consult with your Linux distribution provider for any alternative patches or mitigations they may have.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
