Strix
69K

CVE-2026-98399

Unknown

Last modified

CVE-2026-98399 is a vulnerability of currently unknown severity. 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.

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 099b765139929efdcf232f8870804accf8c4cdc5, < 41647864e62b28388ecccc23a82f0e0a091f4ef2; >= 099b765139929efdcf232f8870804accf8c4cdc5, < aed56fa3108b7095e6a048e134981506c056a6cb; >= 099b765139929efdcf232f8870804accf8c4cdc5, < 8d7988e8116c3d29d9e02ca9d37ee84577643f2d; >= 099b765139929efdcf232f8870804accf8c4cdc5, < 280ff19853440d59e031cd8fe161e81305721262; >= 099b765139929efdcf232f8870804accf8c4cdc5, < 37f61b71cbc0caefc01022a19ee56fc2510e2e6e
LinuxLinux2.6.30

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-98399?
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.
How severe is CVE-2026-98399?
Severity scoring for CVE-2026-98399 is pending analysis.
How do I fix CVE-2026-98399?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-98399?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST