Silent data corruption via lost completion length
Published Sep 11, 2026 · Updated Sep 11, 2026
Data corruption in the Linux s390 DASD driver allows attackers to receive zero-filled data after partial ESE read recovery. dasd_default_erp_postaction() copies recovered request state back to the original request but omits proc_bytes, so __dasd_cleanup_cqr() treats an incomplete transfer as complete instead of requeuing the remainder. The condition requires an s390 system using an ESE DASD where a read of an unallocated track partially completes and enters ERP recovery; unread bytes are silently returned as zeros.
Summary
What happened
Data corruption in the Linux s390 DASD driver allows attackers to receive zero-filled data after partial ESE read recovery. dasd_default_erp_postaction() copies recovered request state back to the original request but omits proc_bytes, so __dasd_cleanup_cqr() treats an incomplete transfer as complete instead of requeuing the remainder. The condition requires an s390 system using an ESE DASD where a read of an unallocated track partially completes and enters ERP recovery; unread bytes are silently returned as zeros.
The record
- CVE
- CVE-2026-89456
- Published
- Sep 11, 2026
- Updated
- Sep 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 11, 2026CVE publishedPublication date reported by the CVE source.
- Sep 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.4.26 <5.5
- Affected versionversion=5.5.10 <5.6
- Affected versionversion=5.6
- Affected versionversion=5e6bdd37c5526ef01326df5dabb93011ee89237e <15ec03452c18e8d288e519837d21b308300d74b2
- Affected versionversion=5e6bdd37c5526ef01326df5dabb93011ee89237e <6fb5ba2e7e43173a3761e46f091070a8185efa14
- Affected versionversion=5e6bdd37c5526ef01326df5dabb93011ee89237e <ceafb262475ac6cb3a7d07b1102608be2b216b99
- Affected versionversion=5e6bdd37c5526ef01326df5dabb93011ee89237e <d6b8778b1b82aa3a8dbf8612080f635b834bd16b
- Affected versionversion=5f7c9989f11305aaa43e0f4378f4f070022a9f2b
- Affected versionversion=fbbacd0dcbc3ae9398c569dbea96ae4b5ad97e04
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo