s390/dasd: Do not complete a failed ESE read as successful
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5e6bdd37c5526ef01326df5dabb93011ee89237e · < 52b331c99baac653ca794bd8487c8ec4de8db203| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
s390/dasd: Do not complete a failed ESE read as successful
dasd_int_handler() completes an NRF read of an unallocated ESE track by calling ese_read() and unconditionally marking the request DASD_CQR_SUCCESS. dasd_eckd_ese_read() can return an error before it has zeroed the destination buffer: a failed sense-data parse or a current track outside the requested range both return early, leaving the destination pages untouched. The request is still completed successfully, so the block layer is handed stale / uninitialized memory instead of zeros.
Check the ese_read() return value and fail the request through the normal error path instead of forcing DASD_CQR_SUCCESS.
From the CVE record · Linux
The Linux kernel’s s390/dasd driver can report a failed read of an unallocated ESE track as successful, returning stale or uninitialized memory instead of zeros. This can occur when sense-data parsing fails or the current track is outside the requested range. The input does not specify attacker access requirements or user interaction.
Engineers running the Linux kernel with s390/dasd ESE devices should check their deployments; affected versions are not specified.