Use-after-free of transaction_t race in jbd2

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1001330: jbd2: fix use-after-free of transaction_t race. Affects Kernel versions >= 4f98186848707f530669238d90e0562d92a78aab, < bff94c57bd130e3062afa94414c2294871314096. 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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The jbd2 (journaling block device 2) is a component of the Linux Kernel that provides support for file system journaling. It ensures the consistency and integrity of file systems by logging changes before they are committed to disk. The transaction_t structure is used to represent a journaling transaction in jbd2. However, a use-after-free vulnerability has been discovered in the race condition of the transaction_t structure, potentially leading to security issues.

Vulnerability Detail

The use-after-free vulnerability in jbd2 arises from a race condition in the handling of the transaction_t structure. This vulnerability can be exploited by an attacker to corrupt memory or execute arbitrary code. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability was introduced in Linux Kernel version v5.17 by commit 4f98186848707f530669238d90e0562d92a78aab and has been fixed in version v5.17.1 by commit bff94c57bd130e3062afa94414c2294871314096.

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 at the moment.

Conclusion

The use-after-free of transaction_t race vulnerability in jbd2 can potentially lead to security issues. It is recommended to update the Linux Kernel to version v5.17.1 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

jbd2 (journaling block device 2) is a component of the Linux Kernel that provides support for file system journaling. It ensures the consistency and integrity of file systems by logging changes before they are committed to disk.

A use-after-free vulnerability occurs when a program continues to use a memory region after it has been freed. This can lead to memory corruption or the execution of arbitrary code.

This vulnerability can be exploited by an attacker to corrupt memory or execute arbitrary code. However, the impact and attack plausibility have not been proven yet.

This vulnerability was introduced in Linux Kernel version v5.17 by commit 4f98186848707f530669238d90e0562d92a78aab.

Yes, this vulnerability has been fixed in Linux Kernel version v5.17.1 by commit bff94c57bd130e3062afa94414c2294871314096.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

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