Memory Leak Vulnerability in MIPS Kernel
Summary
GSD-2022-1001841: MIPS: pgalloc: fix memory leak caused by pgd_free(). Affects Kernel versions >= f9cb654cb550b7b87e8608b14fc3eca432429ffe, < d29cda15cab086d82d692de016f7249545d4b6b4. 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 MIPS kernel is a component of the Linux operating system that supports the MIPS architecture. It provides essential functionality for managing memory allocation and deallocation. The vulnerability in question is related to the pgalloc function, which is responsible for allocating page tables. Due to a coding error, the function fails to free memory properly, leading to a memory leak.
Vulnerability Detail
The vulnerability arises from a memory leak caused by the pgd_free() function in the MIPS pgalloc implementation. When page tables are deallocated, the function fails to release the associated memory, resulting in a gradual accumulation of unreleased memory. This can lead to resource exhaustion and potential denial-of-service conditions. The vulnerability was introduced in version v5.9 of the Linux Kernel and is fixed in version v5.15.33.
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 a workaround, users can mitigate the impact of the vulnerability by limiting the usage of affected functionality or by monitoring system resources closely to detect any signs of resource exhaustion. However, applying the official fix is strongly recommended to ensure complete resolution of the vulnerability.
Conclusion
The memory leak vulnerability in the MIPS Kernel can lead to resource exhaustion and potential denial-of-service conditions. It is crucial to update the Linux Kernel to version v5.15.33 or later to address this issue. Users can also utilize the Vulert Playground (https://vulert.com/scanner) to check if their system is affected by 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 memory leak, potentially causing resource exhaustion and denial-of-service conditions.
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 analyze and alert you if the vulnerability is present.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the fix as soon as possible to prevent any potential exploitation.
The vulnerability itself does not provide remote code execution capabilities. However, if an attacker can gain access to the affected system, they may be able to leverage the memory leak to exhaust system resources and disrupt normal operation.
While applying the official fix is the recommended approach, users can mitigate the impact by closely monitoring system resources and implementing resource usage limits for affected functionality.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
