Vulnerability · Published May 8, 2026 · Assigned by Linux

CVE-2026-43288ext4: move ext4_percpu_param_init() before ext4_mb_init()

Medium 5.5

In plain English

A medium-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 3% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.1%top 97.3% 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: move ext4_percpu_param_init() before ext4_mb_init() When running `kvm-xfstests -c ext4/1k -C 1 generic/383` with the `DOUBLE_CHECK` macro defined, the following panic is triggered: ================================================================== EXT4-fs error (device vdc): ext4_validate_block_bitmap:423: comm mount: bg 0: bad block bitmap checksum BUG: unable to handle page fault for address: ff110000fa2cc000 PGD 3e01067 P4D 3e02067 PUD 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 0 UID: 0 PID: 2386 Comm: mount Tainted: G W 6.18.0-gba65a4e7120a-dirty #1152 PREEMPT(none) RIP: 0010:percpu_counter_add_batch+0x13/0xa0 Call Trace: <TASK> ext4_mark_group_bitmap_corrupted+0xcb/0xe0 ext4_validate_block_bitmap+0x2a1/0x2f0 ext4_read_block_bitmap+0x33/0x50 mb_group_bb_bitmap_alloc+0x33/0x80 ext4_mb_add_groupinfo+0x190/0x250 ext4_mb_init_backend+0x87/0x290 ext4_mb_init+0x456/0x640 __ext4_fill_super+0x1072/0x1680 ext4_fill_super+0xd3/0x280 get_tree_bdev_flags+0x132/0x1d0 vfs_get_tree+0x29/0xd0 vfs_cmd_create+0x59/0xe0 __do_sys_fsconfig+0x4f6/0x6b0 do_syscall_64+0x50/0x1f0 entry_SYSCALL_64_after_hwframe+0x76/0x7e ================================================================== This issue can be reproduced using the following commands: mkfs.ext4 -F -q -b 1024 /dev/sda 5G tune2fs -O quota,project /dev/sda mount /dev/sda /tmp/test With DOUBLE_CHECK defined, mb_group_bb_bitmap_alloc() reads and validates the block bitmap. When the validation fails, ext4_mark_group_bitmap_corrupted() attempts to update sbi->s_freeclusters_counter. However, this percpu_counter has not been initialized yet at this point, which leads to the panic described above. Fix this by moving the execution of ext4_percpu_param_init() to occur before ext4_mb_init(), ensuring the per-CPU counters are initialized before they are used.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.190-1DEBIAN-CVE-2026-43288
Debian:13linux6.12.85-1DEBIAN-CVE-2026-43288
Debian:14linux6.19.6-1DEBIAN-CVE-2026-43288
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux6.8.0-134.134UBUNTU-CVE-2026-43288
Ubuntu:25.10linuxno fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-aws6.8.0-1060.63UBUNTU-CVE-2026-43288
Ubuntu:25.10linux-awsno fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1060.63~22.04.1UBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-azure6.8.0-1063.71UBUNTU-CVE-2026-43288
Ubuntu:25.10linux-azureno fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1063.71~22.04.1UBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-azure-fde6.8.0-1062.69UBUNTU-CVE-2026-43288
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-azure-fde-6.86.8.0-1062.69~22.04.1UBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-gcp6.8.0-1063.69UBUNTU-CVE-2026-43288
Ubuntu:25.10linux-gcpno fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1063.69~22.04.1UBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-gke6.8.0-1058.64UBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1045.48UBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-136.136~22.04.1UBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-ibm6.8.0-1060.61UBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1060.61~22.04.1UBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-134.134.1UBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-134.134.1~22.04.1UBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1058.61UBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1058.61~22.04.1UBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1058.61.1UBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1029.30UBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-oracle6.8.0-1057.58UBUNTU-CVE-2026-43288
Ubuntu:25.10linux-oracleno fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1057.58~22.04.1UBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-raspi6.8.0-1060.64UBUNTU-CVE-2026-43288
Ubuntu:25.10linux-raspino fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-43288
Ubuntu:25.10linux-realtimeno fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-43288
Ubuntu:25.10linux-riscvno fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-134.134~22.04.1UBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-43288
Ubuntu:24.04:LTSlinux-xilinx6.8.0-1032.33UBUNTU-CVE-2026-43288
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-43288

Affected products (as reported)

VendorProductVersions
Linux Linux d5e03cbb0c88cd1be39f2adc37d602230045964b – before 0b3d80c56957862ba477ca0ce30c12cad9179c2bd5e03cbb0c88cd1be39f2adc37d602230045964b – before 0d5fcb063cdabb9aeaa8554b7fedad2092c4150ed5e03cbb0c88cd1be39f2adc37d602230045964b – before 9e9fb259bcddf459a0168f4a964e979e500a68a5d5e03cbb0c88cd1be39f2adc37d602230045964b – before bf5b609524497c195f801cd5707252384aed8149d5e03cbb0c88cd1be39f2adc37d602230045964b – before aec095f3cc6cf209effd93278ce35be27db81d73d5e03cbb0c88cd1be39f2adc37d602230045964b – before 270564513489d98b721a1e4a10017978d5213bff
Linux Linux 3.17

References