Memory Leak Vulnerability in jffs2_do_mount_fs

Kernel Updated 02 Oct 2025

Summary

24/04/2022
N/A
No i
Unrated
Not published

GSD-2022-1002512: jffs2: fix memory leak in jffs2_do_mount_fs. Affects Kernel versions >= e631ddba588783edd521c5a89f7b2902772fb691, < 2a9d8184458562e6bf2f40d0e677fc85e2dd3834. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The jffs2_do_mount_fs function is part of the Journalling Flash File System 2 (JFFS2) in the Linux Kernel. JFFS2 is a file system specifically designed for use with flash memory devices. It provides features such as wear leveling and garbage collection to optimize the lifespan of the flash memory. The jffs2_do_mount_fs function is responsible for mounting the JFFS2 file system. However, a memory leak vulnerability has been discovered in this function.

Vulnerability Detail

The memory leak vulnerability in jffs2_do_mount_fs allows an attacker to cause a denial of service (DoS) condition by repeatedly mounting and unmounting a specially crafted JFFS2 file system. This can lead to exhaustion of system memory resources, resulting in system instability or a complete system crash. The vulnerability was introduced in version v2.6.15 of the Linux Kernel and has been fixed in version v4.9.311.

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 known workaround for this vulnerability. It is recommended to update the Linux Kernel to the fixed version.

Conclusion

The memory leak vulnerability in jffs2_do_mount_fs can be fixed by updating the Linux Kernel to version v4.9.311 or later. It is recommended to apply the fix as soon as possible to prevent potential denial of service (DoS) attacks. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

JFFS2 is the Journalling Flash File System 2, a file system specifically designed for use with flash memory devices. It provides features such as wear leveling and garbage collection to optimize the lifespan of the flash memory.

The memory leak vulnerability in jffs2_do_mount_fs can lead to a denial of service (DoS) condition, causing system instability or a complete system crash.

To fix the vulnerability, it is recommended to update the Linux Kernel to version v4.9.311 or later.

There is no known workaround for this vulnerability. It is recommended to update the Linux Kernel to the fixed version.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability without requiring access to the code or installation.

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