Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-89458

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 38 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 5e6bdd37c5526ef01326df5dabb93011ee89237e – < 8cb96cffceead3cbd0541154d7ecc5e6474edda1
    • affected 5e6bdd37c5526ef01326df5dabb93011ee89237e – < 77168af195d04b34c6de62b874624e74d64cef8d
    • affected 5e6bdd37c5526ef01326df5dabb93011ee89237e – < 921ff697bb6f7067059793becf8b2d00de71ce41
    • affected 5e6bdd37c5526ef01326df5dabb93011ee89237e – < 55f4df40178cdfede0d7ae848fbab00efa9b95c1
    • affected 5e6bdd37c5526ef01326df5dabb93011ee89237e – < c9adf8399732306dfc97b3adb4778038743e3f5e
    • affected 5e6bdd37c5526ef01326df5dabb93011ee89237e – < 52b331c99baac653ca794bd8487c8ec4de8db203
    • affected 5e6bdd37c5526ef01326df5dabb93011ee89237e – < b0d94dd6e82df396e2254c8b0f25eff7d19c2e7f
    • affected 5e6bdd37c5526ef01326df5dabb93011ee89237e – < cddb447c62466f3076938ce120028d7b591f9f37
    • affected fbbacd0dcbc3ae9398c569dbea96ae4b5ad97e04
    • affected 5f7c9989f11305aaa43e0f4378f4f070022a9f2b
    • affected 5.4.26 – < 5.5
    • affected 5.5.10 – < 5.6
  • Linux · Linux

    • affected 5.6
    • unaffected < 5.6
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89458 badge
[![CVE-2026-89458](https://cveledger.app/badge/CVE-2026-89458.svg)](https://cveledger.app/cve/CVE-2026-89458)

Record last updated .