Vulnerability in mm/mempolicy package: mpol_new leak in shared_policy_replace
Summary
GSD-2022-1001678: mm/mempolicy: fix mpol_new leak in shared_policy_replace. Affects Kernel versions >= 42288fe366c4f1ce7522bc9f27d0bc2a81c55264, < 198932a14aeb19a15cf19e51e151d023bc4cd648. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The mm/mempolicy package is a part of the Linux Kernel ecosystem. It provides memory management policies for processes in the Linux operating system. These policies determine how memory is allocated and accessed by different processes. The shared_policy_replace function in the package is responsible for replacing the shared memory policy. However, a vulnerability has been discovered in this function that can lead to a memory leak.
Vulnerability Detail
The vulnerability, identified as GSD-2022-1001678, originates from a memory leak in the shared_policy_replace function of the mm/mempolicy package. When this function is called, it fails to properly release the memory allocated for the new memory policy (mpol_new). This can result in a gradual depletion of system memory, leading to performance degradation and potential denial-of-service attacks. The vulnerability was introduced in version v3.8 of the Linux Kernel and has been fixed in version v5.15.34.
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
No specific workaround has been mentioned for this vulnerability.
Conclusion
In conclusion, the mm/mempolicy package in the Linux Kernel is vulnerable to a memory leak issue in the shared_policy_replace function. This vulnerability can lead to performance degradation and potential denial-of-service attacks. It is crucial to update the Linux Kernel to version v5.15.34 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a gradual depletion of system memory, resulting in performance degradation and potential denial-of-service attacks.
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 to the playground, and it will alert you in real-time if the vulnerability is detected.
As of now, there is no known exploit for this vulnerability. However, it is recommended to apply the fix as soon as possible to mitigate any potential risks.
It is not recommended to manually patch the vulnerability without updating the entire Linux Kernel. The fix for this vulnerability is included in the updated kernel version v5.15.34. Applying the patch manually may introduce other compatibility issues or incomplete fixes.
You can find more information about this vulnerability, including the source code changes and commit details, in the vulnerability database maintained by the Cloud Security Alliance: https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1001xxx/GSD-2022-1001678.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
