CVE-2026-72369
CVE CVE-2026-72369EUVD EUVD-2026-59268Published 2026-08-15T05:56:05.000ZLast changed 2026-08-17T05:43:23.000ZCVSS 7.8
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 7.1.5; 6.19.6 <6.20; patch: 6.6.145; f57ccd4657c7f082dc47e5b9e18a883bb5f9118f <959c95340a9e19cd333b4c18935fdeecbb2f319d; 7.0; 31fefc18096cdc5549cfa54964d90e0b3229aedc <abe3536a4bedcc43de80b6d4d7e3d57e9ba382a5; 2bb588cede1c1969e49c0a2822c8cb8b346b7682 <a11ebaab50d27d6c4c78506f84ff36452e0b901d; patch: 6.12.97; 5.10.252 <5.11; 6.18.16 <6.18.40; 8c97a6ddc95690a938ded44b4e3202f03f15078c <fb3e566cafc38fe3ba35e6843a2d529a3748870c; patch: 7.2; a051ecf5c5b0387840dc210413ed3bc7fbdaa69c; 8c97a6ddc95690a938ded44b4e3202f03f15078c <8a29e60e2176b02e04f8737c8b32b696230eb0c5; d791c544efd6b9c944b43cf7f502e5bcb02fb941; 6.6.128 <6.6.145; patch: 6.18.40; 5.15.202 <5.16; 66c7c239c65341f99ae388d4d53dc9df2bcb9925; 1efc128ee4adbc23e082715425ff895449d233bc; 6.1.165 <6.2; 6.12.75 <6.12.97; patch: 0
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.