Memory Leak Vulnerability in fsl_ifc Package
Summary
GSD-2021-1001179: memory: fsl_ifc: fix leak of IO mapping on probe failure. Affects Kernel versions >= a20cbdeffce247a2b6fb83cd8d22433994068565, < 28f71fd81ebd3b386bf5c7c5539664156f7d72c1. 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 fsl_ifc package is a memory management component in the Linux Kernel. It provides functionality for handling Input/Output (IO) mappings. IO mappings are used to establish direct memory access between devices and the CPU. The fsl_ifc package is commonly used in systems with Freescale (now NXP) processors. This vulnerability in the fsl_ifc package can lead to a memory leak when the probe process fails.
Vulnerability Detail
The vulnerability in the fsl_ifc package occurs when the probe process fails. In such cases, IO mappings are not properly released, resulting in a memory leak. This can lead to a gradual depletion of available memory resources, potentially causing system instability or denial of service. The vulnerability was introduced in version v3.3 of the Linux Kernel and has been fixed in version v5.13.4.
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 provided for this vulnerability. Updating the Linux Kernel to the fixed version is the recommended solution.
Conclusion
The memory leak vulnerability in the fsl_ifc package can lead to a gradual depletion of available memory resources, potentially causing system instability or denial of service. It is crucial to update the Linux Kernel to version v5.13.4 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can result in a memory leak, leading to a gradual depletion of available memory resources. This can potentially cause system instability or denial of service.
The vulnerability was introduced in version v3.3 of the Linux Kernel. All versions between v3.3 and v5.13.4 are affected.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground and it will provide real-time alerts for open-source vulnerabilities.
Yes, a patch is available in version v5.13.4 of the Linux Kernel. It is recommended to update to this version or a later one 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.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.