s390/dasd: Propagate partial completion length across ERP recovery
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5e6bdd37c5526ef01326df5dabb93011ee89237e · < ceafb262475ac6cb3a7d07b1102608be2b216b99| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
s390/dasd: Propagate partial completion length across ERP recovery
dasd_default_erp_postaction() copies the timing and device state from the finished ERP request back to the original request but drops proc_bytes. A request that was partially completed, an ESE read of a not-yet-allocated track returns fewer bytes than requested, and then recovered through the ERP chain loses its partial-completion length. __dasd_cleanup_cqr() then sees proc_bytes == 0 and completes the whole request instead of requeueing the remainder, silently returning zeroed data for the part that was never read.
Carry proc_bytes over to the original request like the other per-request state.
From the CVE record · Linux
The Linux kernel’s s390 DASD error recovery path can lose the length of a partially completed request. If an ESE read of a not-yet-allocated track completes only partly and then goes through recovery, the kernel can return zeroed data for the unread portion instead of requeueing it. The input does not describe an attacker, authentication requirement, or user interaction.
Engineers running Linux systems that use s390 DASD should check their kernel; affected versions were not provided.