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-89457s390/dasd: Guard sysfs discipline callbacks against unallocated private data

Description

In the Linux kernel, the following vulnerability has been resolved: s390/dasd: Guard sysfs discipline callbacks against unallocated private data Several sysfs show/store handlers call a discipline callback that dereferences device->private, either directly or through the DASD_DEFINE_ATTR() macro. During dasd_generic_set_online() the discipline is assigned before check_device() allocates device->private, so an unprivileged read of one of these world-readable attributes in that window dereferences a NULL pointer and panics. Guard the dereference inside each callback that actually touches device->private.

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 (15 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 c729696bcf8b23450043dd9c9972c15e53419ae4 – < 644b666c202cce12ccfcf9ded67089b18f4f7659
    • affected c729696bcf8b23450043dd9c9972c15e53419ae4 – < 4a042d8e5f34282577ece50515cea8bb1246914d
    • affected c729696bcf8b23450043dd9c9972c15e53419ae4 – < bd8b4572528f9604a13bf3c7c2a167f5cf222f72
    • affected c729696bcf8b23450043dd9c9972c15e53419ae4 – < 57db27ccc162afe0726cffec0ae62e410ed2d0e9
    • affected c729696bcf8b23450043dd9c9972c15e53419ae4 – < 536407b272402af679155910d7fdeeb4834eefb9
    • affected c729696bcf8b23450043dd9c9972c15e53419ae4 – < 6452c13646af7c13d7f6668b6690cfb2427e7f7b
    • affected c729696bcf8b23450043dd9c9972c15e53419ae4 – < 449f3bada7a9fad8b8cdf4bb20baf27ee9ca56c5
    • affected c729696bcf8b23450043dd9c9972c15e53419ae4 – < 2a1780f9fc2493bd34c418a0be6fc58943afcecf
  • Linux · Linux

    • affected 5.3
    • unaffected < 5.3
    • 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-89457 badge
[![CVE-2026-89457](https://cveledger.app/badge/CVE-2026-89457.svg)](https://cveledger.app/cve/CVE-2026-89457)

Record last updated .