{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98399 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98399 is a vulnerability in Linux, published on 14 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-98399 and fix it if it is affected.\n\nWhat it is: CVE-2026-98399 is a vulnerability in Linux, published on 14 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-98399 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98399/ (Markdown: https://insights.sbomify.com/CVE-2026-98399/index.md)","id":"CVE-2026-98399","markdown":"https://insights.sbomify.com/CVE-2026-98399/index.md","name":"CVE-2026-98399","record":{"aliases":["AZL-108129","BELL-CVE-2026-98399","DEBIAN-CVE-2026-98399","GHSA-wvr7-cc68-fmx4","UBUNTU-CVE-2026-98399"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A NULL pointer dereference in the Linux kernel s390 IPL code can cause a denial of service during stand-alone dumps when no re-IPL parameter block is provided.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"s390/ipl: Fix NULL deref in dump_reipl without re-IPL parm block","id":"CVE-2026-98399","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"s390/ipl: Fix NULL deref in kdump without re-IPL parm block","id":"CVE-2026-98400"},"packages":[],"prev":{"headline":"locking/lockdep: Invalidate stale class_cache entries for zapped classes","id":"CVE-2026-98398"},"products":["Linux"],"published":"2026-10-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A NULL pointer dereference in the Linux kernel s390 IPL code can cause a denial of service during stand-alone dumps when no re-IPL parameter block is provided.","url":"https://insights.sbomify.com/CVE-2026-98399/"}