Double Free Vulnerability in ubifs

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1002031: ubifs: rename_whiteout: Fix double free for whiteout_ui->data. Affects Kernel versions >= 9e0a1fff8db56eaaebb74b4a3ef65f86811c4798, < a90e2dbe66d2647ff95a0442ad2e86482d977fd8. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The ubifs package is a file system designed for use on flash memory devices. It is commonly used in embedded systems and provides features such as compression, encryption, and wear leveling. The vulnerability in question affects the rename_whiteout function in ubifs, which is responsible for handling whiteout entries. Whiteouts are special entries used to mark files or directories as deleted in a union file system. This vulnerability allows an attacker to trigger a double free condition, potentially leading to a use-after-free vulnerability and subsequent code execution.

Vulnerability Detail

The vulnerability arises due to a double free issue in the rename_whiteout function of ubifs. When processing a whiteout entry, the function attempts to free the memory associated with the entry's data. However, due to a programming error, the same memory is freed twice, resulting in a double free condition. An attacker can exploit this vulnerability by creating a specially crafted whiteout entry, causing the double free condition to occur. This can lead to memory corruption and potentially allow the attacker to execute arbitrary code or crash the system.

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

As a workaround, users can avoid the exploitation of this vulnerability by disabling the use of union file systems or by restricting access to the affected functionality. However, applying the official patch or updating to the latest version is the recommended solution.

Conclusion

The double free vulnerability in ubifs can lead to memory corruption and potential code execution. It is crucial to update the Linux Kernel to the latest version or apply the provided patch to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

ubifs is a file system designed for use on flash memory devices. It provides features such as compression, encryption, and wear leveling.

A double free vulnerability occurs when a program attempts to free the same memory block twice. This can lead to memory corruption and potentially allow an attacker to execute arbitrary code or crash the system.

An attacker can exploit this vulnerability by creating a specially crafted whiteout entry, triggering a double free condition and potentially allowing for code execution or system crashes.

Yes, this vulnerability has been fixed in Linux Kernel version v5.10.110 by commit a90e2dbe66d2647ff95a0442ad2e86482d977fd8.

To protect your system, it is recommended to update the Linux Kernel to version v5.10.110 or later. This will ensure that the vulnerable code is replaced with the patched version.

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