Use-after-free vulnerability in jffs2_clear_xattr_subsystem in Kernel

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1002138: jffs2: fix use-after-free in jffs2_clear_xattr_subsystem. Affects Kernel versions >= aa98d7cf59b5b0764d3502662053489585faf2fe, < 7bb7428dd73991bf4b3a7a61b493ca50046c2b13. 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 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 overall stability and security of the system. The jffs2_clear_xattr_subsystem function is a part of the Journalling Flash File System 2 (JFFS2) subsystem in the Kernel. JFFS2 is a file system specifically designed for flash memory devices, providing efficient storage and retrieval of data. However, a use-after-free vulnerability has been discovered in the jffs2_clear_xattr_subsystem function, which can potentially be exploited by attackers to execute arbitrary code or cause a denial-of-service (DoS) condition.

Vulnerability Detail

The use-after-free vulnerability in jffs2_clear_xattr_subsystem arises when the function attempts to clear extended attributes (xattrs) associated with a file in the JFFS2 file system. Due to a flaw in the implementation, the function does not properly handle the deallocation of memory, leading to a use-after-free condition. An attacker can potentially exploit this vulnerability by crafting a malicious file that triggers the use-after-free condition, leading to arbitrary code execution or a DoS condition. The impact and attack plausibility of this vulnerability have not been proven yet.

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 mentioned for this vulnerability. However, applying the recommended fix by updating the Kernel to the latest version is the best course of action.

Conclusion

The use-after-free vulnerability in jffs2_clear_xattr_subsystem in the Kernel can potentially lead to arbitrary code execution or a denial-of-service (DoS) condition. It is crucial to update the Kernel to version v5.10.110 or later to fix this vulnerability. If immediate updating is not possible, following general security best practices and monitoring for any suspicious activity can help mitigate the risks. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability can range from arbitrary code execution to a denial-of-service (DoS) condition. However, the actual impact and attack plausibility have not been proven yet.

You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) to the playground, and it will provide real-time alerts for open-source vulnerabilities, including this one.

As of now, there is no known exploit for this vulnerability. However, it is essential to apply the recommended fix to mitigate any potential risks.

If you cannot immediately update the Kernel, it is recommended to follow general security best practices, such as restricting access to vulnerable systems, implementing network-level protections, and monitoring for any suspicious activity.

You can find more information about this vulnerability in the Open Source Vulnerability Database (OSVDB) entry with ID GSD-2022-1002138. The link to the database entry is provided in the references section of this report.

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