Stefan Haberland

**Name of the Vulnerable Software and Affected Versions** Linux kernel (affected versions not specified) **Description** The issue concerns the Linux kernel, specifically the s390/dasd component, where the device queue is not protected against concurrent access. In the `dasd profile start()` function, the amount of requests on the device queue is counted, but this access is unprotected, leading to potential kernel panics due to incorrect pointer accesses, especially with parallel I/O and alias devices enabled. The fix involves taking the device lock before accessing the queue and counting requests, and checking for a valid profile data pointer earlier to avoid unnecessary locking. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Linux kernel (affected versions not specified) **Description** The issue is related to a resource management error in the s390/dasd component of the Linux kernel. It is caused by a race window between the `dasd alias get start dev()` function and the ` lcu update()` function, which sets the `pavgroup` pointer to NULL. This can lead to a denial of service. The `pavgroup` pointer is checked at the entrance of the `dasd alias get start dev()` function, but without holding the `lcu->lock`. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Linux kernel (affected versions not specified) **Description** The issue is related to a missing discipline function in the s390/dasd component of the Linux kernel. This leads to a crash with an illegal operation exception in dasd device tasklet when the path verification function is called for a FBA or DIAG device. The problem arises because the verify path function was renamed for ECKD but not for FBA and DIAG. The fix involves defining a wrapper function for dasd generic verify path(). **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.