Vulnerability · Published May 27, 2026 · Assigned by Linux

CVE-2026-45920ext4: fix dirtyclusters double decrement on fs shutdown

High 7.8

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 4% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)7.8High
Exploit odds (30 days)0.1%top 96.1% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: ext4: fix dirtyclusters double decrement on fs shutdown fstests test generic/388 occasionally reproduces a warning in ext4_put_super() associated with the dirty clusters count: WARNING: CPU: 7 PID: 76064 at fs/ext4/super.c:1324 ext4_put_super+0x48c/0x590 [ext4] Tracing the failure shows that the warning fires due to an s_dirtyclusters_counter value of -1. IOW, this appears to be a spurious decrement as opposed to some sort of leak. Further tracing of the dirty cluster count deltas and an LLM scan of the resulting output identified the cause as a double decrement in the error path between ext4_mb_mark_diskspace_used() and the caller ext4_mb_new_blocks(). First, note that generic/388 is a shutdown vs. fsstress test and so produces a random set of operations and shutdown injections. In the problematic case, the shutdown triggers an error return from the ext4_handle_dirty_metadata() call(s) made from ext4_mb_mark_context(). The changed value is non-zero at this point, so ext4_mb_mark_diskspace_used() does not exit after the error bubbles up from ext4_mb_mark_context(). Instead, the former decrements both cluster counters and returns the error up to ext4_mb_new_blocks(). The latter falls into the !ar->len out path which decrements the dirty clusters counter a second time, creating the inconsistency. To avoid this problem and simplify ownership of the cluster reservation in this codepath, lift the counter reduction to a single place in the caller. This makes it more clear that ext4_mb_new_blocks() is responsible for acquiring cluster reservation (via ext4_claim_free_clusters()) in the !delalloc case as well as releasing it, regardless of whether it ends up consumed or returned due to failure.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.170-1DEBIAN-CVE-2026-45920
Debian:13linux6.12.85-1DEBIAN-CVE-2026-45920
Debian:14linux6.18.14-1DEBIAN-CVE-2026-45920
Ubuntu:22.04:LTSlinux5.15.0-186.196UBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux6.8.0-136.136UBUNTU-CVE-2026-45920
Ubuntu:25.10linuxno fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-aws5.15.0-1112.119UBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-aws6.8.0-1061.64UBUNTU-CVE-2026-45920
Ubuntu:25.10linux-awsno fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1061.64~22.04.1UBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-azure5.15.0-1117.126UBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-azure6.8.0-1063.71UBUNTU-CVE-2026-45920
Ubuntu:25.10linux-azureno fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1063.71~22.04.1UBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1117.126UBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-azure-fde6.8.0-1062.69UBUNTU-CVE-2026-45920
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-azure-fde-6.86.8.0-1062.69~22.04.1UBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-gcp5.15.0-1112.122UBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-gcp6.8.0-1064.72UBUNTU-CVE-2026-45920
Ubuntu:25.10linux-gcpno fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1064.72~22.04.1UBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-gke5.15.0-1108.114UBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-gke6.8.0-1059.67UBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1095.103UBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1046.50UBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-136.136~22.04.1UBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-ibm5.15.0-1106.110UBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-ibm6.8.0-1061.62UBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1061.62~22.04.1UBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1107.113UBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-kvm5.15.0-1104.109UBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-184.194UBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-136.136.2UBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-136.136.2~22.04.1UBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1107.108UBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1059.62UBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1059.62~22.04.1UBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1059.62.1UBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1064.66UBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1030.31UBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1053.53UBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-oracle5.15.0-1109.115UBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-oracle6.8.0-1058.61UBUNTU-CVE-2026-45920
Ubuntu:25.10linux-oracleno fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1058.61~22.04.1UBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-raspi5.15.0-1106.109UBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-raspi6.8.0-1061.65UBUNTU-CVE-2026-45920
Ubuntu:25.10linux-raspino fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-45920
Ubuntu:25.10linux-realtimeno fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-45920
Ubuntu:25.10linux-riscvno fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-136.136~22.04.3UBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-vmware6.8.0-1008.8UBUNTU-CVE-2026-45920
Ubuntu:24.04:LTSlinux-xilinx6.8.0-1033.34UBUNTU-CVE-2026-45920
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1075.79UBUNTU-CVE-2026-45920

Affected products (as reported)

VendorProductVersions
Linux Linux 0087d9fb3f29f59e8d42c8b058376d80e5adde4c – before 523d5a4df3c649fa305c89efb552ec62a1ce9d3d0087d9fb3f29f59e8d42c8b058376d80e5adde4c – before ca408af08544d96769c93a3d81a7f63f61129e950087d9fb3f29f59e8d42c8b058376d80e5adde4c – before 55576fa14771d33994c29a9ae960e07bb3f56c200087d9fb3f29f59e8d42c8b058376d80e5adde4c – before dbc4e10619ed87a50e637b96f2e574df36a7a7690087d9fb3f29f59e8d42c8b058376d80e5adde4c – before 61e372122b6d95aec940fdaea0a16f988f3598970087d9fb3f29f59e8d42c8b058376d80e5adde4c – before 3924aea2c33df3864929c1acd178bfc29d8f005f0087d9fb3f29f59e8d42c8b058376d80e5adde4c – before 81982a11406c5da6c6e2b188028e7056e16b71280087d9fb3f29f59e8d42c8b058376d80e5adde4c – before 94a8cea54cd935c54fa2fba70354757c0fc245e3
Linux Linux 2.6.29

References