Minix filesystem support in the Linux kernel lacks input validation for critical superblock fields, notably s_log_zone_size. The kernel expects this field to be zero but accepts other values, and additional data fields lack sanity checking. A crafted superblock with invalid values can cause the kernel to calculate incorrect sizes and indices, leading to memory corruption or a crash. This would result in a denial‑of‑service by unconditionally crashing the host during a mount operation.

All Linux kernel distributions that still use the unmodified fs/minix implementation are affected. The vulnerability is present in kernel versions prior to the application of the commit that adds sanity checks and potentially in util‑linux utility versions that generate Minix superblocks without enforcing the zero s_log_zone_size rule. The exact affected releases are not enumerated, but any pre‑patch kernel with the vulnerable code path is at risk.

Official security metrics are not published; no CVSS or EPSS score is available, and the vulnerability is not listed in the CISA KEV catalog. The absence of input validation suggests that crafting a malicious superblock would be relatively straightforward, but the lack of a documented exploit and KEV status indicates no confirmed exploitation in the wild. Nonetheless, the potential to crash the kernel during a mount operation makes the vulnerability high‑impact from an availability standpoint.