CVE-2021-46945

ext4: always panic when errors=panic is specified

State
Published
Severity
Not scored
Published
Feb 27, 2024
Updated
May 11, 2026
Reserved
Feb 25, 2024

Read the record on cve.org

Description

In the Linux kernel, the following vulnerability has been resolved:

ext4: always panic when errors=panic is specified

Before commit 014c9caa29d3 ("ext4: make ext4_abort() use __ext4_error()"), the following series of commands would trigger a panic:

1. mount /dev/sda -o ro,errors=panic test 2. mount /dev/sda -o remount,abort test

After commit 014c9caa29d3, remounting a file system using the test mount option "abort" will no longer trigger a panic. This commit will restore the behaviour immediately before commit 014c9caa29d3. (However, note that the Linux kernel's behavior has not been consistent; some previous kernel versions, including 5.4 and 4.19 similarly did not panic after using the mount option "abort".)

This also makes a change to long-standing behaviour; namely, the following series commands will now cause a panic, when previously it did not:

1. mount /dev/sda -o ro,errors=panic test 2. echo test > /sys/fs/ext4/sda/trigger_fs_error

However, this makes ext4's behaviour much more consistent, so this is a good thing.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 014c9caa29d3a44e0de695c99ef18bec3e887d52 to before 64e1eebe2131183174f4fbb6b1491355f96c6cdeAffected
  • 014c9caa29d3a44e0de695c99ef18bec3e887d52 to before 1e9ea8f4637026b8e965128953f2da061ccae9c4Affected
  • 014c9caa29d3a44e0de695c99ef18bec3e887d52 to before ac2f7ca51b0929461ea49918f27c11b680f28995Affected
LinuxLinux
  • 5.11Affected
  • before 5.11Not affected
  • 5.11.20 through 5.11.*Not affected
  • 5.12.3 through 5.12.*Not affected
  • 5.13 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.