ext4: Don't BUG if someone dirty pages without asking ext4 first
Summary
GSD-2022-1001793: ext4: don't BUG if someone dirty pages without asking ext4 first. Affects Kernel versions < a0856764dc1276ad2dc7891288c2e9246bf11a37. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The ext4 package is a file system driver for the Linux Kernel. It provides support for the fourth extended file system (ext4) and is widely used in Linux distributions. The ext4 file system is known for its performance, scalability, and reliability. However, a vulnerability has been discovered in the ext4 driver that could potentially lead to system crashes or other unexpected behavior.
Vulnerability Detail
The vulnerability in the ext4 driver occurs when someone dirty pages without asking ext4 first. This can trigger a BUG condition, causing the system to crash or behave unpredictably. An attacker could potentially exploit this vulnerability to cause a denial-of-service (DoS) attack or gain elevated privileges on the affected system. The vulnerability has been fixed in Linux Kernel version v5.15.33 by commit a0856764dc1276ad2dc7891288c2e9246bf11a37.
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 →
Conclusion
The ext4 driver vulnerability can lead to system crashes or other unexpected behavior. It is important to update the Linux Kernel to version v5.15.33 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
ext4 is a file system driver for the Linux Kernel that provides support for the fourth extended file system (ext4). It is widely used in Linux distributions.
The vulnerability can lead to system crashes or other unexpected behavior. An attacker could potentially exploit it to cause a denial-of-service (DoS) attack or gain elevated privileges.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and it will provide real-time alerts for open-source vulnerabilities.
Yes, the vulnerability has been fixed in Linux Kernel version v5.15.33 by commit a0856764dc1276ad2dc7891288c2e9246bf11a37.
To update the Linux Kernel, you can download the latest kernel source code from the official Linux Kernel repository and compile it for your system. Alternatively, you can check if your system's package manager provides an updated kernel package and install it using the appropriate package management commands.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
