When a corrupted inode on an ext2 filesystem has zero link count, a non‑zero mode and no deletion time, ext2_iget() does not reject it. The kernel then passes it to the VFS and triggers a WARN_ON in drop_nlink during unlink, rename or rmdir. This warning indicates an internal inconsistency and may signal kernel instability, but the CVE description does not confirm a crash or denial of service. The vulnerability is therefore seen as a potential disruptive issue rather than an explicit DoS, based only on the observed warning traces provided.

All Linux kernel versions that use the ext2 filesystem before the advertised fix are affected. The issue appears in the ext2 subsystem of the kernel, so any host that mounts ext2 or ext3 partitions with such corrupted inodes could be impacted.

The exploit requires a crafted ext2 image that contains a malformed inode. An attacker with the ability to control the contents of such an image or who can mount a malicious filesystem locally can trigger the warning. The EPSS score is not available and the vulnerability is not in the CISA KEV catalog. While the probability of exploitation is uncertain, repeated triggering of the warning may lead to kernel instability or service disruption on affected systems. The likely attack vector is the presence of a malicious ext2 filesystem image, as inferred from the exploit description.