s390/ipl: Fix NULL deref in dump_reipl without re-IPL parm block
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's s390 dump re-IPL path can dereference a NULL pointer when an IPL type does not provide a re-IPL parameter block, as may occur with HMC FTP boot or QEMU direct kernel boot. The stand-alone dumper may then enter disabled wait after completing the dump. The input does not describe an attacker, access requirements, or user interaction.
Engineers running the Linux kernel on s390 systems using stand-alone dumps should check whether their kernel is affected; affected versions are not specified.