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-98399s390/ipl: Fix NULL deref in dump_reipl without re-IPL parm block

Description

In the Linux kernel, the following vulnerability has been resolved: s390/ipl: Fix NULL deref in dump_reipl without re-IPL parm block Unlike kdump, which passes the re-IPL parameter block through os_info, the stand-alone dump passes it through the IPL parm block address and checksum in lowcore. Some IPL types, like HMC FTP boot or QEMU direct kernel boot, might not provide an IPL parameter block. In this case reipl_type_init() selects IPL_TYPE_UNKNOWN and reipl_block_actual remains NULL. Nevertheless, dump_reipl_run() unconditionally dereferences it when preparing the lowcore fields. This may happen to work by chance when address zero contains readable lowcore data. A zero IPL parameter block address is then stored in lowcore, causing the stand-alone dumper to enter disabled wait after completing the dump. Explicitly store a zero IPL parameter block address and checksum when no re-IPL parameter block is available. This does not change the behavior: the stand-alone dumper completes the dump and halts, while valid re-IPL parameter blocks continue to be handled as before.

Timeline

  1. ID reserved

    By Linux

  2. · 19 days later

    Published

  3. · 5 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.20% · top 90% of all CVEs (18 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 099b765139929efdcf232f8870804accf8c4cdc5 – < 41647864e62b28388ecccc23a82f0e0a091f4ef2
    • affected 099b765139929efdcf232f8870804accf8c4cdc5 – < aed56fa3108b7095e6a048e134981506c056a6cb
    • affected 099b765139929efdcf232f8870804accf8c4cdc5 – < 8d7988e8116c3d29d9e02ca9d37ee84577643f2d
    • affected 099b765139929efdcf232f8870804accf8c4cdc5 – < 280ff19853440d59e031cd8fe161e81305721262
    • affected 099b765139929efdcf232f8870804accf8c4cdc5 – < 37f61b71cbc0caefc01022a19ee56fc2510e2e6e
  • Linux · Linux

    • affected 2.6.30
    • unaffected < 2.6.30
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .