Memory Leak Vulnerability in fsl_ifc Package

Kernel Updated 02 Oct 2025

Summary

03/08/2021
N/A
No i
Unrated
Not published

GSD-2021-1001324: memory: fsl_ifc: fix leak of private memory on probe failure. Affects Kernel versions >= a20cbdeffce247a2b6fb83cd8d22433994068565, < 443f6ca6fd186b4fa4e6f377b6e19a91feb1a0d5. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The fsl_ifc package is a memory management component in the Linux Kernel. It is responsible for handling memory allocation and deallocation for the Freescale Integrated Flash Controller (IFC) driver. The IFC driver provides support for accessing the flash memory on Freescale processors. The vulnerability in the fsl_ifc package leads to a memory leak when the probe process fails. This can result in the exhaustion of system memory resources and potential system instability.

Vulnerability Detail

The vulnerability in the fsl_ifc package occurs when the probe process fails. In this scenario, private memory allocated by the fsl_ifc driver is not properly deallocated, leading to a memory leak. An attacker could potentially exploit this vulnerability by repeatedly triggering the probe failure, causing the system to run out of memory and potentially crashing. The vulnerability was introduced in version v3.3 of the Linux Kernel and is fixed in version v5.4.134.

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 disable the fsl_ifc driver if it is not required for their system. This can be done by blacklisting the fsl_ifc module or removing it from the kernel configuration. However, this workaround should only be considered if the fsl_ifc driver is not essential for the system's functionality.

Conclusion

The memory leak vulnerability in the fsl_ifc package can lead to system instability and potential crashes. It is crucial to update the Linux Kernel to version v5.4.134 or later to fix this vulnerability. Alternatively, users can disable the fsl_ifc driver if it is not required for their system. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can lead to a memory leak, causing the system to run out of memory and potentially crashing.

You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply upload your package-lock.json file and Vulert will analyze it for any open-source vulnerabilities, including this memory leak vulnerability in the fsl_ifc package.

Yes, the vulnerability is fixed in version v5.4.134 of the Linux Kernel. It is recommended to update to this version or later to mitigate the vulnerability.

Yes, as a workaround, you can disable the fsl_ifc driver if it is not required for your system. This can be done by blacklisting the fsl_ifc module or removing it from the kernel configuration.

There are no known exploits for this vulnerability at the moment. However, it is still important to apply the necessary updates and patches to mitigate the risk.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback