{"api_version":"1","generated_at":"2026-10-27T04:32:26+00:00","cve":"CVE-2026-98399","urls":{"html":"https://cve.report/CVE-2026-98399","api":"https://cve.report/api/cve/CVE-2026-98399.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-98399","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-98399"},"summary":{"title":"s390/ipl: Fix NULL deref in dump_reipl without re-IPL parm block","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/ipl: Fix NULL deref in dump_reipl without re-IPL parm block\n\nUnlike kdump, which passes the re-IPL parameter block through os_info,\nthe stand-alone dump passes it through the IPL parm block address and\nchecksum in lowcore.\n\nSome IPL types, like HMC FTP boot or QEMU direct kernel boot, might not\nprovide an IPL parameter block. In this case reipl_type_init() selects\nIPL_TYPE_UNKNOWN and reipl_block_actual remains NULL. Nevertheless,\ndump_reipl_run() unconditionally dereferences it when preparing the\nlowcore fields. This may happen to work by chance when address zero\ncontains readable lowcore data. A zero IPL parameter block address is\nthen stored in lowcore, causing the stand-alone dumper to enter disabled\nwait after completing the dump.\n\nExplicitly store a zero IPL parameter block address and checksum when no\nre-IPL parameter block is available. This does not change the behavior:\nthe stand-alone dumper completes the dump and halts, while valid re-IPL\nparameter blocks continue to be handled as before.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-10-14 14:17:50","updated_at":"2026-10-19 10:18:44"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/aed56fa3108b7095e6a048e134981506c056a6cb","name":"https://git.kernel.org/stable/c/aed56fa3108b7095e6a048e134981506c056a6cb","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/41647864e62b28388ecccc23a82f0e0a091f4ef2","name":"https://git.kernel.org/stable/c/41647864e62b28388ecccc23a82f0e0a091f4ef2","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/280ff19853440d59e031cd8fe161e81305721262","name":"https://git.kernel.org/stable/c/280ff19853440d59e031cd8fe161e81305721262","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/8d7988e8116c3d29d9e02ca9d37ee84577643f2d","name":"https://git.kernel.org/stable/c/8d7988e8116c3d29d9e02ca9d37ee84577643f2d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/37f61b71cbc0caefc01022a19ee56fc2510e2e6e","name":"https://git.kernel.org/stable/c/37f61b71cbc0caefc01022a19ee56fc2510e2e6e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-98399","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98399","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 099b765139929efdcf232f8870804accf8c4cdc5 41647864e62b28388ecccc23a82f0e0a091f4ef2 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 099b765139929efdcf232f8870804accf8c4cdc5 aed56fa3108b7095e6a048e134981506c056a6cb git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 099b765139929efdcf232f8870804accf8c4cdc5 8d7988e8116c3d29d9e02ca9d37ee84577643f2d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 099b765139929efdcf232f8870804accf8c4cdc5 280ff19853440d59e031cd8fe161e81305721262 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 099b765139929efdcf232f8870804accf8c4cdc5 37f61b71cbc0caefc01022a19ee56fc2510e2e6e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2.6.30","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 2.6.30 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6.158 6.6.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.111 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.53 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.7 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["arch/s390/kernel/ipl.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"41647864e62b28388ecccc23a82f0e0a091f4ef2","status":"affected","version":"099b765139929efdcf232f8870804accf8c4cdc5","versionType":"git"},{"lessThan":"aed56fa3108b7095e6a048e134981506c056a6cb","status":"affected","version":"099b765139929efdcf232f8870804accf8c4cdc5","versionType":"git"},{"lessThan":"8d7988e8116c3d29d9e02ca9d37ee84577643f2d","status":"affected","version":"099b765139929efdcf232f8870804accf8c4cdc5","versionType":"git"},{"lessThan":"280ff19853440d59e031cd8fe161e81305721262","status":"affected","version":"099b765139929efdcf232f8870804accf8c4cdc5","versionType":"git"},{"lessThan":"37f61b71cbc0caefc01022a19ee56fc2510e2e6e","status":"affected","version":"099b765139929efdcf232f8870804accf8c4cdc5","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["arch/s390/kernel/ipl.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"2.6.30"},{"lessThan":"2.6.30","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.6.*","status":"unaffected","version":"6.6.158","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.111","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.53","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.7","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.6.158","versionStartIncluding":"2.6.30","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.111","versionStartIncluding":"2.6.30","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.53","versionStartIncluding":"2.6.30","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.7","versionStartIncluding":"2.6.30","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3","versionStartIncluding":"2.6.30","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/ipl: Fix NULL deref in dump_reipl without re-IPL parm block\n\nUnlike kdump, which passes the re-IPL parameter block through os_info,\nthe stand-alone dump passes it through the IPL parm block address and\nchecksum in lowcore.\n\nSome IPL types, like HMC FTP boot or QEMU direct kernel boot, might not\nprovide an IPL parameter block. In this case reipl_type_init() selects\nIPL_TYPE_UNKNOWN and reipl_block_actual remains NULL. Nevertheless,\ndump_reipl_run() unconditionally dereferences it when preparing the\nlowcore fields. This may happen to work by chance when address zero\ncontains readable lowcore data. A zero IPL parameter block address is\nthen stored in lowcore, causing the stand-alone dumper to enter disabled\nwait after completing the dump.\n\nExplicitly store a zero IPL parameter block address and checksum when no\nre-IPL parameter block is available. This does not change the behavior:\nthe stand-alone dumper completes the dump and halts, while valid re-IPL\nparameter blocks continue to be handled as before."}],"providerMetadata":{"dateUpdated":"2026-10-19T09:18:52.784Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/41647864e62b28388ecccc23a82f0e0a091f4ef2"},{"url":"https://git.kernel.org/stable/c/aed56fa3108b7095e6a048e134981506c056a6cb"},{"url":"https://git.kernel.org/stable/c/8d7988e8116c3d29d9e02ca9d37ee84577643f2d"},{"url":"https://git.kernel.org/stable/c/280ff19853440d59e031cd8fe161e81305721262"},{"url":"https://git.kernel.org/stable/c/37f61b71cbc0caefc01022a19ee56fc2510e2e6e"}],"title":"s390/ipl: Fix NULL deref in dump_reipl without re-IPL parm block","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-98399","datePublished":"2026-10-14T13:26:00.278Z","dateReserved":"2026-09-25T10:25:14.346Z","dateUpdated":"2026-10-19T09:18:52.784Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-14 14:17:50","lastModifiedDate":"2026-10-19 10:18:44","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"98399","Ordinal":"1","Title":"s390/ipl: Fix NULL deref in dump_reipl without re-IPL parm block","CVE":"CVE-2026-98399","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"98399","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ns390/ipl: Fix NULL deref in dump_reipl without re-IPL parm block\n\nUnlike kdump, which passes the re-IPL parameter block through os_info,\nthe stand-alone dump passes it through the IPL parm block address and\nchecksum in lowcore.\n\nSome IPL types, like HMC FTP boot or QEMU direct kernel boot, might not\nprovide an IPL parameter block. In this case reipl_type_init() selects\nIPL_TYPE_UNKNOWN and reipl_block_actual remains NULL. Nevertheless,\ndump_reipl_run() unconditionally dereferences it when preparing the\nlowcore fields. This may happen to work by chance when address zero\ncontains readable lowcore data. A zero IPL parameter block address is\nthen stored in lowcore, causing the stand-alone dumper to enter disabled\nwait after completing the dump.\n\nExplicitly store a zero IPL parameter block address and checksum when no\nre-IPL parameter block is available. This does not change the behavior:\nthe stand-alone dumper completes the dump and halts, while valid re-IPL\nparameter blocks continue to be handled as before.","Type":"Description","Title":"s390/ipl: Fix NULL deref in dump_reipl without re-IPL parm block"}]}}}