CVE-2026-89458

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

N/A
Published: September 11, 2026 at 07:43 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.4.265.5.105.65e6bdd37c5526ef01326df5dabb93011ee89237e5f7c9989f11305aaa43e0f4378f4f070022a9f2bfbbacd0dcbc3ae9398c569dbea96ae4b5ad97e04
Vendor states this is fixed in 52b331c99baac653ca794bd8487c8ec4de8db203 (fixed)
Vendor states this is fixed in 55f4df40178cdfede0d7ae848fbab00efa9b95c1 (fixed)
Vendor states this is fixed in 77168af195d04b34c6de62b874624e74d64cef8d (fixed)
Vendor states this is fixed in 8cb96cffceead3cbd0541154d7ecc5e6474edda1 (fixed)
Vendor states this is fixed in 921ff697bb6f7067059793becf8b2d00de71ce41 (fixed)
Vendor states this is fixed in b0d94dd6e82df396e2254c8b0f25eff7d19c2e7f (fixed)
Vendor states this is fixed in c9adf8399732306dfc97b3adb4778038743e3f5e (fixed)
Vendor states this is fixed in cddb447c62466f3076938ce120028d7b591f9f37 (fixed)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.6 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.109 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card