CVE-2026-43068

published 5 May 2026 · updated 13 Nov 2026

ext4: avoid allocate block from corrupted group in ext4_mb_find_by_goal()

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 5.10.253, Kernel 5.15.203, Kernel 6.1.168 and 12 more.

In the Linux kernel, the following vulnerability has been resolved: ext4: avoid allocate block from corrupted group in ext4_mb_find_by_goal() There's issue as follows: ... EXT4-fs (mmcblk0p1): Delayed block allocation failed for inode 206 at logical offset 0 with max blocks 1 with error 117 EXT4-fs (mmcblk0p1): This should not happen!! Data will be lost EXT4-fs (mmcblk0p1): Delayed block allocation failed for inode 206 at logical offset 0 with max blocks 1 with error 117 EXT4-fs (mmcblk0p1): This should not happen!! Data will be lost EXT4-fs (mmcblk0p1): Delayed block allocation failed for inode 206 at logical offset 0 with max blocks 1 with error 117 EXT4-fs (mmcblk0p1): This should not happen!! Data will be lost EXT4-fs (mmcblk0p1): Delayed block allocation failed for inode 206 at logical offset 0 with max blocks 1 with error 117 EXT4-fs (mmcblk0p1): This should not happen!! Data will be lost EXT4-fs (mmcblk0p1): Delayed block allocation failed for inode 2243 at logical offset 0 with max blocks 1 with error 117 EXT4-fs (mmcblk0p1): This should not happen!! Data will be lost EXT4-fs (mmcblk0p1): Delayed block allocation failed for inode 2239 at logical offset 0 with max blocks 1 with error 117 EXT4-fs (mmcblk0p1): This should not happen!! Data will be lost EXT4-fs (mmcblk0p1): error count since last fsck: 1 EXT4-fs (mmcblk0p1): initial error at time 1765597433: ext4_mb_generate_buddy:760 EXT4-fs (mmcblk0p1): last error at time 1765597433: ext4_mb_generate_buddy:760 ... According to the log analysis, blocks are always requested from the corrupted block group. This may happen as follows: ext4_mb_find_by_goal ext4_mb_load_buddy ext4_mb_load_buddy_gfp ext4_mb_init_cache ext4_read_block_bitmap_nowait ext4_wait_block_bitmap ext4_validate_block_bitmap if (!grp || EXT4_MB_GRP_BBITMAP_CORRUPT(grp)) return -EFSCORRUPTED; // There's no logs. if (err) return err; // Will return error ext4_lock_group(ac->ac_sb, group); if (unlikely(EXT4_MB_GRP_BBITMAP_CORRUPT(e4b->bd_info))) // Unreachable goto out; After commit 9008a58e5dce ("ext4: make the bitmap read routines return real error codes") merged, Commit 163a203ddb36 ("ext4: mark block group as corrupt on block bitmap error") is no real solution for allocating blocks from corrupted block groups. This is because if 'EXT4_MB_GRP_BBITMAP_CORRUPT(e4b->bd_info)' is true, then 'ext4_mb_load_buddy()' may return an error. This means that the block allocation will fail. Therefore, check block group if corrupted when ext4_mb_load_buddy() returns error.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=3.12 <5.10.253, >=5.11 <5.15.203, >=5.16 <6.1.168, >=6.13 <6.18.21, >=6.19 <6.19.11, >=6.2 <6.6.131, >=6.7 <6.12.80, =7.0, >=163a203ddb36c36d4a1c942aececda0cc8d06aa7 <1895f7904be71c48f1e6f338b28f24dabd6b8aeb, >=163a203ddb36c36d4a1c942aececda0cc8d06aa7 <1c0d7c4cde38a887c6d74e0c89ddb25226943c78, >=163a203ddb36c36d4a1c942aececda0cc8d06aa7 <2d31a5073f86a177edf44015e0dedb0c47cfd6d8, >=163a203ddb36c36d4a1c942aececda0cc8d06aa7 <46066e3a06647c5b186cc6334409722622d05c44, >=163a203ddb36c36d4a1c942aececda0cc8d06aa7 <9370207b36d26e45a8c8ef0500706d37036edd6b, >=163a203ddb36c36d4a1c942aececda0cc8d06aa7 <fea6b2e250ff48f10d166011b57a8516ae5438c9, >=163a203ddb36c36d4a1c942aececda0cc8d06aa7 <ffc0a282462d45fee5957621be5afa29752f3b6d, =3.12, >=163a203ddb36c36d4a1c942aececda0cc8d06aa7 <0b84571c886719823d537f05f4f07cad6357c4b75.10.253, 5.15.203, 6.1.168, 6.18.21, 6.19.11, 6.6.131, 6.12.80, 1895f7904be71c48f1e6f338b28f24dabd6b8aeb, 1c0d7c4cde38a887c6d74e0c89ddb25226943c78, 2d31a5073f86a177edf44015e0dedb0c47cfd6d8, 46066e3a06647c5b186cc6334409722622d05c44, 9370207b36d26e45a8c8ef0500706d37036edd6b, fea6b2e250ff48f10d166011b57a8516ae5438c9, ffc0a282462d45fee5957621be5afa29752f3b6d, 0b84571c886719823d537f05f4f07cad6357c4b7
linux-kernel: Kernel>=3.12.0 <5.10.253, >=5.11.0 <5.15.203, >=5.16.0 <6.1.168, >=6.13.0 <6.18.21, >=6.19.0 <6.19.11, >=6.2.0 <6.6.131, >=6.7.0 <6.12.805.10.253, 5.15.203, 6.1.168, 6.18.21, 6.19.11, 6.6.131, 6.12.80

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-43068 severity on Zeptric[![CVE-2026-43068](https://zeptric.io/badge/cve/CVE-2026-43068.svg)](https://zeptric.io/cve/CVE-2026-43068)