Memory Leak in jffs2_do_mount_fs in Kernel
Summary
GSD-2022-1001922: jffs2: fix memory leak in jffs2_do_mount_fs. Affects Kernel versions >= e631ddba588783edd521c5a89f7b2902772fb691, < 4392e8aeebc5a4f8073620bccba7de1b1f6d7c88. 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 Kernel is a critical component of the Linux operating system that provides core functionality and interfaces with hardware devices. It manages system resources, facilitates communication between software and hardware, and enables the execution of user programs. The jffs2 file system is a flash-friendly file system designed for use with embedded systems. It is commonly used in devices such as routers, IoT devices, and network-attached storage (NAS) devices. 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 v5.15.33. The fix involves a commit (4392e8aeebc5a4f8073620bccba7de1b1f6d7c88) that addresses the memory leak issue.
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 necessary to apply the fix by updating the Linux Kernel.
Conclusion
The memory leak vulnerability in jffs2_do_mount_fs can be mitigated by updating the Linux Kernel to version v5.15.33 or later. This will prevent the exploitation of the vulnerability and ensure system stability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a denial-of-service (DoS) condition, causing system instability or a complete system crash.
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 and the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.
Yes, a patch has been released in version v5.15.33 of the Linux Kernel. It is recommended to update to this version or later to fix the vulnerability.
No, the fix for this vulnerability requires updating the Linux Kernel to version v5.15.33 or later. It is not possible to manually apply the fix without updating the entire Kernel.
There are no known exploits for this vulnerability at the time of this report. However, it is important to apply the fix as soon as possible to mitigate the risk.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
