CVE-2026-89458: s390/dasd: Do not complete a failed ESE read as successful

Published Sep 11, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

s390/dasd: Do not complete a failed ESE read as successful

dasdinthandler() completes an NRF read of an unallocated ESE track by calling eseread() and unconditionally marking the request DASDCQRSUCCESS. dasdeckdeseread() 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 eseread() return value and fail the request through the normal error path instead of forcing DASDCQRSUCCESS.

Affected Software

1 affected component
Linux Kernel

Event History

Sep 11, 2026
CVE Published
via MITRE·07:43 PM
Data Sourced
via MITRE·07:43 PM
Description

Frequently Asked Questions

1

Which systems are exposed to this issue?

Systems using the Linux kernel s390 DASD driver are exposed when an NRF read targets an unallocated ESE track and the ESE read helper fails before zeroing the destination buffer.

2

What does an attacker or triggering condition need to cause the problem?

The issue requires an NRF read of an unallocated ESE track plus an error in the ESE read path, such as failed sense-data parsing or a current track outside the requested range. Under those conditions, the request can be reported as successful even though its destination pages were not initialized.

3

What is the impact of a successful-looking failed read?

The block layer may receive stale or uninitialized memory rather than the expected zero-filled data. This can expose data present in the destination pages and can cause consumers to treat invalid read data as valid.

4

How can administrators mitigate the issue if they cannot apply the fix immediately?

The provided information identifies the affected path as s390 DASD NRF reads involving unallocated ESE tracks. Avoiding workloads or configurations that issue those reads is the only mitigation supported by the available data; the permanent fix is to fail the request when ese_read() returns an error.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203