powerpc/papr_scm: Fix leaking nvdimm_events_map elements
Summary
GSD-2022-1002703: powerpc/papr_scm: Fix leaking nvdimm_events_map elements. Affects Kernel versions >= 4c08d4bbc089a95f3f38389c2b79dbc6ab24f10b, < b073096df4dec70d0436321b7093bad27ae91f9e. 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 powerpc/papr_scm package is a component of the Linux Kernel. It provides support for Persistent Memory (PMEM) devices on PowerPC systems. PMEM devices are non-volatile memory devices that can be used as a storage medium. The nvdimm_events_map is a data structure used by the powerpc/papr_scm package to track events related to PMEM devices. However, a vulnerability has been discovered in the package that causes nvdimm_events_map elements to leak, potentially leading to memory corruption or information disclosure.
Vulnerability Detail
The vulnerability in the powerpc/papr_scm package allows nvdimm_events_map elements to leak, which can result in memory corruption or information disclosure. This can be exploited by an attacker to gain unauthorized access to sensitive data or execute arbitrary code. The vulnerability was introduced in version v5.18 of the Linux Kernel and has been fixed in version v5.18.3.
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 recommended to apply the fix by updating the Linux Kernel to the latest version.
Conclusion
The powerpc/papr_scm package in the Linux Kernel is vulnerable to a memory leak issue in the nvdimm_events_map data structure. This vulnerability can lead to memory corruption or information disclosure. To mitigate the risk, it is recommended to update the Linux Kernel to version v5.18.3 or later. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to memory corruption or information disclosure, potentially allowing an attacker to gain unauthorized access to sensitive data or execute arbitrary code.
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 Vulert will analyze it for any open-source vulnerabilities, including this one.
Yes, a patch has been released in version v5.18.3 of the Linux Kernel. It is recommended to update to this version to fix the vulnerability.
There are no known exploits for this vulnerability at the moment. However, it is important to apply the fix as soon as possible to prevent any potential attacks.
This vulnerability was discovered by an automated ID intended to aid in the discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
