# s390/ipl: Fix NULL deref in kdump without re-IPL parm block

CVE record · `CVE-2026-98400`

- **Identifiers:** `CVE-2026-98400`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 14 Oct 2026
- **Updated:** 19 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 14 Oct 2026, 13:26 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `3b9678472bab86ae654cf2c18d5dd551558045be to before 030e88812435fc5d6aa42eee41fa77b5ea620327` (git)
  - affected: `3b9678472bab86ae654cf2c18d5dd551558045be to before 92d0829eae257544b6b0faccb6e7079c45e22d48` (git)
  - affected: `3b9678472bab86ae654cf2c18d5dd551558045be to before 50f9c40768e84f30d374235b3ee3850a94d9ac29` (git)
  - affected: `3b9678472bab86ae654cf2c18d5dd551558045be to before b6bf82bc5e00afaf836f8bb9a676bffc182a6bbd` (git)
  - affected: `3b9678472bab86ae654cf2c18d5dd551558045be to before 7f918871112e8e7c581e99eb8e545af4e59c8367` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.17`
  - unaffected: `before 4.17` (semver)
  - unaffected: `6.6.158 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.111 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.53 to 6.18.*, inclusive` (semver)
  - unaffected: `7.2.7 to 7.2.*, inclusive` (semver)
  - unaffected: `7.3 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0020, the 9th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 14 Oct 2026. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2026-98400](https://www.cve.org/CVERecord?id=CVE-2026-98400)
- [NVD: CVE-2026-98400](https://nvd.nist.gov/vuln/detail/CVE-2026-98400)

### References from the CNA

- <https://git.kernel.org/stable/c/030e88812435fc5d6aa42eee41fa77b5ea620327>
- <https://git.kernel.org/stable/c/92d0829eae257544b6b0faccb6e7079c45e22d48>
- <https://git.kernel.org/stable/c/50f9c40768e84f30d374235b3ee3850a94d9ac29>
- <https://git.kernel.org/stable/c/b6bf82bc5e00afaf836f8bb9a676bffc182a6bbd>
- <https://git.kernel.org/stable/c/7f918871112e8e7c581e99eb8e545af4e59c8367>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-98400>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-98400/>. Everything for agents: <https://agentprime.io/llms.txt>.
