The kernel's vfio_ccw driver does not enforce bounds checks on indices used for read/write regions. This omission can allow out‑of‑bounds memory accesses, enabling an attacker to read or modify arbitrary kernel memory, which can lead to privilege escalation or system compromise on s390 platforms.

All Linux kernel builds running on s390 architecture that include the vfio_ccw driver before the commit that adds proper bounds checking. The issue has been fixed in later kernel releases; systems should update to the latest stable or mainline kernel that incorporates the commit noted in the supplied references.

The vulnerability involves unchecked user input leading to potential kernel memory corruption. No EPSS score is available, and the vulnerability is not listed in the CISA KEV catalog, so the exploitation probability is currently unknown. However, the lack of bounds checks represents a high severity risk, especially if an attacker can control the index values via any user‑space interface to the vfio_ccw module. The attack vector is likely local or remote through the vfio_ccw interface, though explicit exploitation details are not provided in the data.