Memory Leak in jffs2_do_fill_super in Kernel

Kernel Updated 02 Oct 2025

Summary

28/06/2022
N/A
No i
Unrated
Not published

GSD-2022-1003968: jffs2: fix memory leak in jffs2_do_fill_super. Affects Kernel versions >= e631ddba588783edd521c5a89f7b2902772fb691, < 4da8763a3d2b684c773b72ed80fad40bc264bc40. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The Kernel is a crucial component of the Linux operating system that provides core functionalities and acts as an interface between hardware and software. It manages system resources, facilitates communication between different software components, and ensures the security and stability of the system. The jffs2_do_fill_super function is responsible for initializing the JFFS2 file system superblock, which is used for flash memory storage devices. This vulnerability in jffs2_do_fill_super can lead to a memory leak, causing the system to exhaust available memory resources over time.

Vulnerability Detail

The vulnerability in jffs2_do_fill_super arises from a memory leak issue. When the function is called to initialize the JFFS2 file system superblock, it fails to release allocated memory in certain scenarios. As a result, memory resources are not properly freed, leading to a gradual depletion of available memory. This can eventually cause system instability, performance degradation, and potential denial-of-service conditions. The vulnerability was introduced in version v2.6.15 of the Linux Kernel and has been fixed in version v4.14.283.

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 →

Conclusion

The memory leak vulnerability in jffs2_do_fill_super can have serious consequences for system stability and performance. It is crucial to update the Linux Kernel to version v4.14.283 or later, which includes the necessary fix. By doing so, the system will properly release allocated memory, mitigating the risk of memory exhaustion and potential denial-of-service conditions. For further assistance or support in addressing this vulnerability, 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 gradually exhaust available memory resources. This can result in system instability, performance degradation, and potential denial-of-service conditions.

You can check if your system is affected by this vulnerability by verifying the version of the Linux Kernel installed. If your system is running a version prior to v4.14.283, it is potentially vulnerable. Additionally, you can use vulnerability monitoring tools like Vulert to scan your system and identify any vulnerable components.

At the time of this report, there are no known public exploits specifically targeting this vulnerability. However, it is important to promptly apply the recommended update to mitigate the risk of potential exploitation.

This vulnerability does not have a direct remote exploitation vector. However, if an attacker gains access to the system, they could potentially leverage the memory leak to degrade system performance or launch further attacks.

No specific temporary workaround has been provided for this vulnerability. It is recommended to apply the official update to address the memory leak issue.

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