Data loss via corrupt-group goal reuse
Published May 5, 2026 · Updated May 5, 2026
Improper block allocation in Linux Kernel ext4 allows local users to trigger write failures and data loss through a corrupted group. The ext4_mb_find_by_goal() path returns when ext4_mb_load_buddy() reports a corrupt bitmap, making its later corrupt-group guard unreachable and leaving the bad group as the allocation goal. A local user must exercise writes on an ext4 filesystem with a corrupt block-group bitmap; delayed allocations then fail and unwritten data is lost.
Summary
What happened
Improper block allocation in Linux Kernel ext4 allows local users to trigger write failures and data loss through a corrupted group. The ext4_mb_find_by_goal() path returns when ext4_mb_load_buddy() reports a corrupt bitmap, making its later corrupt-group guard unreachable and leaving the bad group as the allocation goal. A local user must exercise writes on an ext4 filesystem with a corrupt block-group bitmap; delayed allocations then fail and unwritten data is lost.
The record
- CVE
- CVE-2026-43068
- Published
- May 5, 2026
- Updated
- May 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 5, 2026CVE publishedPublication date reported by the CVE source.
- May 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=163a203ddb36c36d4a1c942aececda0cc8d06aa7 <0b84571c886719823d537f05f4f07cad6357c4b7
- Affected versionversion=163a203ddb36c36d4a1c942aececda0cc8d06aa7 <1895f7904be71c48f1e6f338b28f24dabd6b8aeb
- Affected versionversion=163a203ddb36c36d4a1c942aececda0cc8d06aa7 <1c0d7c4cde38a887c6d74e0c89ddb25226943c78
- Affected versionversion=163a203ddb36c36d4a1c942aececda0cc8d06aa7 <2d31a5073f86a177edf44015e0dedb0c47cfd6d8
- Affected versionversion=163a203ddb36c36d4a1c942aececda0cc8d06aa7 <46066e3a06647c5b186cc6334409722622d05c44
- Affected versionversion=163a203ddb36c36d4a1c942aececda0cc8d06aa7 <9370207b36d26e45a8c8ef0500706d37036edd6b
- Affected versionversion=163a203ddb36c36d4a1c942aececda0cc8d06aa7 <fea6b2e250ff48f10d166011b57a8516ae5438c9
- Affected versionversion=163a203ddb36c36d4a1c942aececda0cc8d06aa7 <ffc0a282462d45fee5957621be5afa29752f3b6d
- Affected versionversion=3.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo