Filesystem disruption via corrupted-group block allocation
Published Apr 3, 2024 · Updated Aug 5, 2026
A race condition in the ext4 allocator in Linux allows local users to worsen block-bitmap corruption during allocation. Between ext4_mb_good_group and ext4_mb_try_best_found, the allocator releases the group lock and later uses ac_b_ex without rechecking whether the group bitmap was marked corrupt. Exploitation requires local low-privileged access and corruption during that unlock gap; further allocation can worsen filesystem damage and interrupt availability.
Summary
What happened
A race condition in the ext4 allocator in Linux allows local users to worsen block-bitmap corruption during allocation. Between ext4_mb_good_group and ext4_mb_try_best_found, the allocator releases the group lock and later uses ac_b_ex without rechecking whether the group bitmap was marked corrupt. Exploitation requires local low-privileged access and corruption during that unlock gap; further allocation can worsen filesystem damage and interrupt availability.
The record
- CVE
- CVE-2024-26773
- Published
- Apr 3, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 3, 2024CVE publishedPublication date reported by the CVE source.
- Aug 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 <0184747b552d6b5a14db3b7fcc3b792ce64dedd1
- Affected versionversion=163a203ddb36c36d4a1c942aececda0cc8d06aa7 <21f8cfe79f776287459343e9cfa6055af61328ea
- Affected versionversion=163a203ddb36c36d4a1c942aececda0cc8d06aa7 <260fc96283c0f594de18a1b045faf6d8fb42874d
- Affected versionversion=163a203ddb36c36d4a1c942aececda0cc8d06aa7 <4530b3660d396a646aad91a787b6ab37cf604b53
- Affected versionversion=163a203ddb36c36d4a1c942aececda0cc8d06aa7 <4c21fa60a6f4606f6214a38f50612b17b2f738f5
- Affected versionversion=163a203ddb36c36d4a1c942aececda0cc8d06aa7 <927794a02169778c9c2e7b25c768ab3ea8c1dc03
- Affected versionversion=163a203ddb36c36d4a1c942aececda0cc8d06aa7 <a2576ae9a35c078e488f2c573e9e6821d651fbbe
- Affected versionversion=163a203ddb36c36d4a1c942aececda0cc8d06aa7 <f97e75fa4e12b0aa0224e83fcbda8853ac2adf36
- 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