Vulnerability in Kernel: mm,hwpoison: unmap poisoned page before invalidation
Summary
GSD-2022-1002273: mm,hwpoison: unmap poisoned page before invalidation. Affects Kernel versions >= d1313f5e8fe50ce84ec3eac162873ee028a30631, < d102fcacfcf35d137d07127e223bed8cf0de17a2. 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 system resources and provides an interface for software to interact with hardware. It is responsible for memory management, process scheduling, device drivers, and other essential functions. This vulnerability affects the Kernel's handling of poisoned pages in the mm and hwpoison subsystems.
Vulnerability Detail
The vulnerability arises from a failure to unmap a poisoned page before invalidation. When a page is marked as poisoned, it indicates a hardware error or corruption. However, if the page is not properly unmapped before invalidation, it may still be accessible to attackers. This could potentially lead to unauthorized access, data leakage, or other security breaches. The vulnerability was introduced in version v5.4.189 of the Linux Kernel and has been fixed in version v5.4.189 by commit d102fcacfcf35d137d07127e223bed8cf0de17a2.
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 available for this vulnerability. It is crucial to apply the fix by updating the Linux Kernel to the patched version.
Conclusion
The vulnerability in the Kernel's mm,hwpoison subsystems, which allows for the potential unauthorized access and data leakage, has been addressed in version v5.4.189 of the Linux Kernel. It is crucial to update the Kernel to the patched version to ensure the security and integrity of affected systems. For further assistance, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability could potentially allow attackers to gain unauthorized access, leak sensitive data, or carry out other malicious activities on affected systems.
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 tool will analyze it for any known vulnerabilities, including this one.
At the time of this report, there are no known public exploits for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate any potential risks.
The vulnerability itself does not provide remote exploitation capabilities. However, if an attacker already has access to the system, they could potentially exploit this vulnerability to escalate privileges or perform other malicious actions.
For further support on vulnerability remediation or any other security concerns, you can reach out to info@devnack.com. Our team of experts will be happy to assist you.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
