Filesystem corruption via unlocked buddy fast path
Published May 27, 2026 · Updated May 27, 2026
Race condition in Linux Kernel ext4 allows local users to corrupt filesystem allocation state through block allocation and page migration. The ext4_mb_load_buddy fast path merely increments a folio reference and uses an uptodate buddy folio without locking it, so migration can overlap bitmap writes. Low-privilege access to an ext4 filesystem is sufficient, but exploitation requires sustained allocation I/O and memory pressure that induce the narrow migration race.
Summary
What happened
Race condition in Linux Kernel ext4 allows local users to corrupt filesystem allocation state through block allocation and page migration. The ext4_mb_load_buddy fast path merely increments a folio reference and uses an uptodate buddy folio without locking it, so migration can overlap bitmap writes. Low-privilege access to an ext4 filesystem is sufficient, but exploitation requires sustained allocation I/O and memory pressure that induce the narrow migration race.
The record
- CVE
- CVE-2026-45942
- Published
- May 27, 2026
- Updated
- May 27, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 27, 2026CVE publishedPublication date reported by the CVE source.
- May 27, 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=0 <6.12.75
- Affected versionversion=0 <6.18.14
- Affected versionversion=0 <6.19.4
- Affected versionversion=0 <6.6.130
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <29a07d691d282faf38c33d4b61839b89399110f9
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <57e83bfbe1e412ac42daced2086f3c6f9a17bba0
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bdc56a9c46b2a99c12313122b9352b619a2e719e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c05033cfc5c7699cd4df8d48cef94d01da755f24
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f29709a7a3fc38f5015d850504762cdef0e151f9
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