ext4: Bug in Handling Dirty Pages without Permission

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1002219: ext4: don't BUG if someone dirty pages without asking ext4 first. Affects Kernel versions < 5a016c053f426a73752c3b41b60b497b58694d48. 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 ext4 package is a file system driver for the Linux Kernel. It provides support for the fourth extended file system (ext4), which is commonly used in Linux distributions. The ext4 file system offers improved performance, scalability, and reliability compared to its predecessors. However, a vulnerability has been discovered in the ext4 driver that allows someone to dirty pages without obtaining permission from ext4 first.

Vulnerability Detail

The vulnerability in the ext4 driver arises from a bug that allows unauthorized modification of dirty pages. Dirty pages are memory pages that have been modified but not yet written back to disk. Normally, ext4 should be responsible for handling the dirty pages and ensuring their proper synchronization with the file system. However, due to this bug, an attacker can bypass ext4's permission checks and directly modify the dirty pages. This could lead to data corruption, integrity issues, or even a system crash. 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. The recommended solution is to update the Linux Kernel to the fixed version.

Conclusion

The ext4 driver in the Linux Kernel is vulnerable to a bug that allows unauthorized modification of dirty pages. This could result in data corruption, integrity issues, or system crashes. The vulnerability has been fixed in Linux Kernel version v5.4.189. It is recommended to update the Linux Kernel to this version or a later one that includes the fix. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

ext4 is a file system driver for the Linux Kernel, providing support for the fourth extended file system (ext4). It offers improved performance, scalability, and reliability compared to previous file system versions.

A dirty page refers to a memory page that has been modified but not yet written back to disk. It contains data that needs to be synchronized with the file system.

The impact of this vulnerability could include data corruption, integrity issues, or system crashes. However, the actual impact and attack plausibility have not been proven yet.

To fix this vulnerability, update your Linux Kernel to version v5.4.189 or a later version that includes the fix.

No specific workaround has been mentioned for this vulnerability. Updating the Linux Kernel to the fixed version is the recommended solution.

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