Answer in brief
CVE-2026-98400 records a Unknown severity vulnerability in s390/ipl: Fix NULL deref in kdump without re-IPL parm block. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3b9678472bab86ae654cf2c18d5dd551558045be <030e88812435fc5d6aa42eee41fa77b5ea620327 || >=3b9678472bab86ae654cf2c18d5dd551558045be <92d0829eae257544b6b0faccb6e7079c45e22d48 || >=3b9678472bab86ae654cf2c18d5dd551558045be <50f9c40768e84f30d374235b3ee3850a94d9ac29 || >=3b9678472bab86ae654cf2c18d5dd551558045be <b6bf82bc5e00afaf836f8bb9a676bffc182a6bbd || >=3b9678472bab86ae654cf2c18d5dd551558045be <7f918871112e8e7c581e99eb8e545af4e59c8367 | 030e88812435fc5d6aa42eee41fa77b5ea620327, 92d0829eae257544b6b0faccb6e7079c45e22d48, 50f9c40768e84f30d374235b3ee3850a94d9ac29, b6bf82bc5e00afaf836f8bb9a676bffc182a6bbd, 7f918871112e8e7c581e99eb8e545af4e59c8367 |
| Linux/Linuxgeneric | 4.17 | Not reported |
Published upstream
Oct 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 14, 2026
In the Linux kernel, the following vulnerability has been resolved: s390/ipl: Fix NULL deref in kdump without re-IPL parm block 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. kdump passes the re-IPL parameter block to the dump kernel through os_info. Before commit 3b9678472bab ("s390/ipl: correct kdump reipl block checksum calculation"), the os_info entry was added only for IPL types which initialized reipl_block_actual. That commit moved the os_info update to machine_crash_shutdown(), making it unconditional. As a result, set_os_info_reipl_block() dereferences reipl_block_actual for IPL_TYPE_UNKNOWN. This may happen to work by chance when address zero contains readable lowcore data and the resulting empty os_info entry is ignored by the dump kernel. Skip the os_info update when no re-IPL parameter block is available. Kdump then collect the dump and reboot without setting re-IPL parameter block.
Quoted source text, attributed separately from HOL analysis.