CVE-2026-43068ext4: avoid allocate block from corrupted group in ext4_mb_find_by_goal()
- 5.5MediumCVSS base score
- 0.12%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 4 days later
· 4 days later
Published
- 6 months later
· 6 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.12% · top 98% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 163a203ddb36c36d4a1c942aececda0cc8d06aa7 – < fea6b2e250ff48f10d166011b57a8516ae5438c9
- affected 163a203ddb36c36d4a1c942aececda0cc8d06aa7 – < 0b84571c886719823d537f05f4f07cad6357c4b7
- affected 163a203ddb36c36d4a1c942aececda0cc8d06aa7 – < ffc0a282462d45fee5957621be5afa29752f3b6d
- affected 163a203ddb36c36d4a1c942aececda0cc8d06aa7 – < 2d31a5073f86a177edf44015e0dedb0c47cfd6d8
- affected 163a203ddb36c36d4a1c942aececda0cc8d06aa7 – < 9370207b36d26e45a8c8ef0500706d37036edd6b
- affected 163a203ddb36c36d4a1c942aececda0cc8d06aa7 – < 1895f7904be71c48f1e6f338b28f24dabd6b8aeb
- affected 163a203ddb36c36d4a1c942aececda0cc8d06aa7 – < 1c0d7c4cde38a887c6d74e0c89ddb25226943c78
- affected 163a203ddb36c36d4a1c942aececda0cc8d06aa7 – < 46066e3a06647c5b186cc6334409722622d05c44
- affected 3.12
- unaffected < 3.12
- unaffected 5.10.253 – ≤ 5.10.*
- unaffected 5.15.203 – ≤ 5.15.*
- unaffected 6.1.168 – ≤ 6.1.*
- unaffected 6.6.131 – ≤ 6.6.*
- unaffected 6.12.80 – ≤ 6.12.*
- unaffected 6.18.21 – ≤ 6.18.*
- unaffected 6.19.11 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References8
- https://git.kernel.org/stable/c/fea6b2e250ff48f10d166011b57a8516ae5438c9 (opens in a new tab)
- https://git.kernel.org/stable/c/0b84571c886719823d537f05f4f07cad6357c4b7 (opens in a new tab)
- https://git.kernel.org/stable/c/ffc0a282462d45fee5957621be5afa29752f3b6d (opens in a new tab)
- https://git.kernel.org/stable/c/2d31a5073f86a177edf44015e0dedb0c47cfd6d8 (opens in a new tab)
- https://git.kernel.org/stable/c/9370207b36d26e45a8c8ef0500706d37036edd6b (opens in a new tab)
- https://git.kernel.org/stable/c/1895f7904be71c48f1e6f338b28f24dabd6b8aeb (opens in a new tab)
- https://git.kernel.org/stable/c/1c0d7c4cde38a887c6d74e0c89ddb25226943c78 (opens in a new tab)
- https://git.kernel.org/stable/c/46066e3a06647c5b186cc6334409722622d05c44 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-27370 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-43068)Record last updated .