The fs/minix implementation in the Linux kernel failed to validate the superblock field s_log_zone_size, which is only defined to be zero, and performed insufficient checks on other superblock parameters. An attacker can supply a Minix volume with an invalid s_log_zone_size or corrupted superblock fields, causing the kernel to compute incorrect addresses or sizes during the mount process. This miscalculation can trigger a kernel crash, resulting in a denial of service for the host system.

All Linux kernels that contain the unpatched fs/minix code path are affected, including older releases such as 2.6.12 and any other kernel versions prior to the commit that added the sanity checks. The issue persists in any distribution that ships with the legacy minix filesystem support and has not yet applied the patch.

The assigned CVSS score of 5.5 reflects a medium severity availability flaw, and the EPSS score of less than 1% indicates a low probability of exploitation in the wild. The vulnerability is not listed in the CISA KEV catalog. Based on the description, exploitation requires loading or mounting a malicious Minix volume, which is a local operation performed by the operating system. A local attacker with the ability to mount the filesystem can trigger a crash; remote exploitation would need a mechanism to force the target system to mount the malformed filesystem, which is outside the scope of the current description.