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-1002280: jffs2: fix use-after-free in jffs2_clear_xattr_subsystem. Affects Kernel versions >= aa98d7cf59b5b0764d3502662053489585faf2fe, < 30bf7244acf32f19cb722c39f7bc1c2a9f300422. 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 package is a critical component of the Linux operating system. It provides the core functionality and interfaces for communication between hardware and software. The jffs2_clear_xattr_subsystem function is responsible for clearing the extended attributes subsystem in the JFFS2 file system. Extended attributes allow additional metadata to be associated with files. However, a use-after-free vulnerability has been discovered in this function, which can lead to potential security issues.

Vulnerability Detail

The use-after-free vulnerability in jffs2_clear_xattr_subsystem arises when the function attempts to free a memory object that has already been freed. This can result in the use of invalid memory, leading to various consequences such as crashes, privilege escalation, or arbitrary code execution. Attackers may exploit this vulnerability to gain unauthorized access or disrupt the system's stability. The vulnerability was introduced in version v2.6.18 of the Linux Kernel and has been fixed in version v5.4.189.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.4.189 or later. This can be done by obtaining the latest version from the official Linux Kernel repository and following the installation instructions provided. It is crucial to keep the system up to date with security patches to mitigate the risk of such vulnerabilities.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

No specific workaround has been mentioned for this vulnerability.

Conclusion

The use-after-free vulnerability in jffs2_clear_xattr_subsystem poses a potential security risk in the Kernel package. It is crucial to update the Linux Kernel to the fixed version to mitigate the risk of crashes, privilege escalation, or arbitrary code execution. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The use-after-free vulnerability in jffs2_clear_xattr_subsystem can potentially lead to crashes, privilege escalation, or arbitrary code execution. Attackers may exploit this vulnerability to gain unauthorized access or disrupt the system's stability.

You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and Vulert will analyze it in real-time to identify any open-source vulnerabilities, including this one.

At the time of this report, no known exploits have been disclosed for this specific vulnerability. However, it is crucial to apply the recommended fix to mitigate the risk.

Yes, this vulnerability can be exploited remotely if an attacker can gain access to the affected system.

The primary solution is to update the Linux Kernel to the fixed version. However, if updating is not feasible, additional security measures such as network segmentation, access controls, and intrusion detection systems can help mitigate the risk.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.4.189 or later. This can be done by obtaining the latest version from the official Linux Kernel repository and following the installation instructions provided. It is crucial to keep the system up to date with security patches to mitigate the risk of such vulnerabilities.

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.