A corrupted RAID5 journal can contain payload sizes that exceed the amount of metadata space available, leading to out-of-bounds reads when the kernel processes journal blocks. This vulnerability is an improper bounds check that allows kernel memory to be read beyond the intended buffer, which can expose sensitive information or cause a system crash. The weakness is a classic out-of-bounds reading flaw, often classified as a memory safety violation.

All Linux kernel installations are potentially affected, as the CPE indicates the entire Linux kernel product is impacted. No specific version exclusions are listed, implying that any kernel build containing the mpblk RAID5 code is vulnerable.

The risk is elevated in environments where an attacker can influence or corrupt the RAID5 journal, such as by writing to a block device that the kernel keeps in memory. While no proof‑of‑concept exploit is publicly documented, the nature of the bug means that a local or privileged attacker could read kernel addresses to facilitate further compromise. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog, suggesting that active exploitation is not yet common. Nonetheless, the presence of this bug warrants prompt mitigation due to the potential for information disclosure and system instability.