Kernel panic via Minix bitmap-count overflow
Published Aug 15, 2026 · Updated Aug 15, 2026
Integer overflow in the Minix filesystem in Linux allows local users to panic the kernel by mounting a crafted Minix v3 image. minix_blocks_needed() performs DIV_ROUND_UP() in unsigned arithmetic, so near-UINT_MAX inode or zone counts wrap the bitmap-block result to zero and let minix_fill_super() dereference an unallocated bitmap entry. Exploitation requires local access and permission to mount an attacker-controlled filesystem image, resulting in a system-wide crash.
Summary
What happened
Integer overflow in the Minix filesystem in Linux allows local users to panic the kernel by mounting a crafted Minix v3 image. minix_blocks_needed() performs DIV_ROUND_UP() in unsigned arithmetic, so near-UINT_MAX inode or zone counts wrap the bitmap-block result to zero and let minix_fill_super() dereference an unallocated bitmap entry. Exploitation requires local access and permission to mount an attacker-controlled filesystem image, resulting in a system-wide crash.
The record
- CVE
- CVE-2026-72369
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-190, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 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=1efc128ee4adbc23e082715425ff895449d233bc
- Affected versionversion=2bb588cede1c1969e49c0a2822c8cb8b346b7682 <a11ebaab50d27d6c4c78506f84ff36452e0b901d
- Affected versionversion=31fefc18096cdc5549cfa54964d90e0b3229aedc <abe3536a4bedcc43de80b6d4d7e3d57e9ba382a5
- Affected versionversion=5.10.252 <5.11
- Affected versionversion=5.15.202 <5.16
- Affected versionversion=6.1.165 <6.2
- Affected versionversion=6.12.75 <6.12.97
- Affected versionversion=6.18.16 <6.18.40
- Affected versionversion=6.19.6 <6.20
- Affected versionversion=6.6.128 <6.6.145
- Affected versionversion=66c7c239c65341f99ae388d4d53dc9df2bcb9925
- Affected versionversion=7.0
- Affected versionversion=8c97a6ddc95690a938ded44b4e3202f03f15078c <8a29e60e2176b02e04f8737c8b32b696230eb0c5
- Affected versionversion=8c97a6ddc95690a938ded44b4e3202f03f15078c <fb3e566cafc38fe3ba35e6843a2d529a3748870c
- Affected versionversion=a051ecf5c5b0387840dc210413ed3bc7fbdaa69c
- Affected versionversion=d791c544efd6b9c944b43cf7f502e5bcb02fb941
- Affected versionversion=f57ccd4657c7f082dc47e5b9e18a883bb5f9118f <959c95340a9e19cd333b4c18935fdeecbb2f319d
What conditions does exploitation require?
What is affected?
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