s390/dasd: fix error recovery leading to data corruption on ESE devices
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5e2b17e712cf10cc3cc98fde28a88e8f1a1267e9 · < 5d4a304338daf83ace2887aaacafd66fe99ed5cc| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
s390/dasd: fix error recovery leading to data corruption on ESE devices
Extent Space Efficient (ESE) or thin provisioned volumes need to be formatted on demand during usual IO processing.
The dasd_ese_needs_format function checks for error codes that signal the non existence of a proper track format.
The check for incorrect length is to imprecise since other error cases leading to transport of insufficient data also have this flag set. This might lead to data corruption in certain error cases for example during a storage server warmstart.
Fix by removing the check for incorrect length and replacing by explicitly checking for invalid track format in transport mode.
Also remove the check for file protected since this is not a valid ESE handling case.
From the CVE record · Linux
The Linux kernel’s s390/dasd error recovery can misidentify certain errors as indicating an unformatted track on Extent Space Efficient (ESE) volumes. During normal I/O, this can lead to data corruption in certain error cases, such as a storage server warmstart. The input does not describe an attacker, authentication requirement, or user interaction.
Operators running Linux kernels with s390/dasd and ESE volumes should check their exposure; affected versions are not specified.