Answer in brief
CVE-2026-72369 records a Unknown severity vulnerability in minix: avoid overflow in bitmap block count calculation. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2bb588cede1c1969e49c0a2822c8cb8b346b7682 <a11ebaab50d27d6c4c78506f84ff36452e0b901d || >=f57ccd4657c7f082dc47e5b9e18a883bb5f9118f <959c95340a9e19cd333b4c18935fdeecbb2f319d || >=31fefc18096cdc5549cfa54964d90e0b3229aedc <abe3536a4bedcc43de80b6d4d7e3d57e9ba382a5 || >=8c97a6ddc95690a938ded44b4e3202f03f15078c <8a29e60e2176b02e04f8737c8b32b696230eb0c5 || >=8c97a6ddc95690a938ded44b4e3202f03f15078c <fb3e566cafc38fe3ba35e6843a2d529a3748870c || a051ecf5c5b0387840dc210413ed3bc7fbdaa69c || d791c544efd6b9c944b43cf7f502e5bcb02fb941 || 66c7c239c65341f99ae388d4d53dc9df2bcb9925 || 1efc128ee4adbc23e082715425ff895449d233bc || >=6.6.128 <6.6.145 || >=6.12.75 <6.12.97 || >=6.18.16 <6.18.40 || >=5.10.252 <5.11 || >=5.15.202 <5.16 || >=6.1.165 <6.2 || >=6.19.6 <6.20 | a11ebaab50d27d6c4c78506f84ff36452e0b901d, 959c95340a9e19cd333b4c18935fdeecbb2f319d, abe3536a4bedcc43de80b6d4d7e3d57e9ba382a5, 8a29e60e2176b02e04f8737c8b32b696230eb0c5, fb3e566cafc38fe3ba35e6843a2d529a3748870c, 6.6.145, 6.12.97, 6.18.40, 5.11, 5.16, 6.2, 6.20 |
| Linux/Linuxgeneric | 7.0 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: minix: avoid overflow in bitmap block count calculation minix_check_superblock() uses minix_blocks_needed() to verify that the on-disk imap and zmap block counts are large enough for the advertised inode and zone counts. The helper currently performs DIV_ROUND_UP() in unsigned int arithmetic. A Minix v3 image can set s_ninodes or s_zones near UINT_MAX so the addition inside DIV_ROUND_UP() wraps to zero. That makes a zero imap/zmap block count look valid, after which minix_fill_super() can dereference s_imap[0] or s_zmap[0] even though no bitmap buffers were allocated. Impact: mounting a crafted Minix v3 image whose s_ninodes or s_zones is near UINT_MAX makes minix_check_superblock() accept a zero bitmap-block count and minix_fill_super() dereference s_imap[0]/s_zmap[0], panicking the kernel. The divisor is the bitmap capacity in bits, blocksize * 8, which is always a power of two: minix_fill_super() obtains the block size through sb_set_blocksize(), and blk_validate_block_size() rejects any size that is not a power of two. Use DIV_ROUND_UP_POW2(), which divides before adding the round-up term and so cannot overflow for a power-of-two divisor.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-72369 records a Unknown severity vulnerability in minix: avoid overflow in bitmap block count calculation. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2bb588cede1c1969e49c0a2822c8cb8b346b7682 <a11ebaab50d27d6c4c78506f84ff36452e0b901d || >=f57ccd4657c7f082dc47e5b9e18a883bb5f9118f <959c95340a9e19cd333b4c18935fdeecbb2f319d || >=31fefc18096cdc5549cfa54964d90e0b3229aedc <abe3536a4bedcc43de80b6d4d7e3d57e9ba382a5 || >=8c97a6ddc95690a938ded44b4e3202f03f15078c <8a29e60e2176b02e04f8737c8b32b696230eb0c5 || >=8c97a6ddc95690a938ded44b4e3202f03f15078c <fb3e566cafc38fe3ba35e6843a2d529a3748870c || a051ecf5c5b0387840dc210413ed3bc7fbdaa69c || d791c544efd6b9c944b43cf7f502e5bcb02fb941 || 66c7c239c65341f99ae388d4d53dc9df2bcb9925 || 1efc128ee4adbc23e082715425ff895449d233bc || >=6.6.128 <6.6.145 || >=6.12.75 <6.12.97 || >=6.18.16 <6.18.40 || >=5.10.252 <5.11 || >=5.15.202 <5.16 || >=6.1.165 <6.2 || >=6.19.6 <6.20 | a11ebaab50d27d6c4c78506f84ff36452e0b901d, 959c95340a9e19cd333b4c18935fdeecbb2f319d, abe3536a4bedcc43de80b6d4d7e3d57e9ba382a5, 8a29e60e2176b02e04f8737c8b32b696230eb0c5, fb3e566cafc38fe3ba35e6843a2d529a3748870c, 6.6.145, 6.12.97, 6.18.40, 5.11, 5.16, 6.2, 6.20 |
| Linux/Linuxgeneric | 7.0 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: minix: avoid overflow in bitmap block count calculation minix_check_superblock() uses minix_blocks_needed() to verify that the on-disk imap and zmap block counts are large enough for the advertised inode and zone counts. The helper currently performs DIV_ROUND_UP() in unsigned int arithmetic. A Minix v3 image can set s_ninodes or s_zones near UINT_MAX so the addition inside DIV_ROUND_UP() wraps to zero. That makes a zero imap/zmap block count look valid, after which minix_fill_super() can dereference s_imap[0] or s_zmap[0] even though no bitmap buffers were allocated. Impact: mounting a crafted Minix v3 image whose s_ninodes or s_zones is near UINT_MAX makes minix_check_superblock() accept a zero bitmap-block count and minix_fill_super() dereference s_imap[0]/s_zmap[0], panicking the kernel. The divisor is the bitmap capacity in bits, blocksize * 8, which is always a power of two: minix_fill_super() obtains the block size through sb_set_blocksize(), and blk_validate_block_size() rejects any size that is not a power of two. Use DIV_ROUND_UP_POW2(), which divides before adding the round-up term and so cannot overflow for a power-of-two divisor.
Quoted source text, attributed separately from HOL analysis.