CVE-2026-98399: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-wvr7-cc68-fmx4
Share
Published
Advisory Summary

CVE-2026-98399 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-98399 at a Glance

CVE Identifier CVE-2026-98399
GHSA Identifier GHSA-wvr7-cc68-fmx4
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-98399

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-98399, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2026-98399 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98399
git.kernel.org/stable/c/280ff19853... WEB
https://git.kernel.org/stable/c/280ff19853440d59e031cd8fe161e81305721262
git.kernel.org/stable/c/37f61b71cb... WEB
https://git.kernel.org/stable/c/37f61b71cbc0caefc01022a19ee56fc2510e2e6e
git.kernel.org/stable/c/41647864e6... WEB
https://git.kernel.org/stable/c/41647864e62b28388ecccc23a82f0e0a091f4ef2
git.kernel.org/stable/c/8d7988e811... WEB
https://git.kernel.org/stable/c/8d7988e8116c3d29d9e02ca9d37ee84577643f2d
git.kernel.org/stable/c/aed56fa310... WEB
https://git.kernel.org/stable/c/aed56fa3108b7095e6a048e134981506c056a6cb

Frequently Asked Questions

What is CVE-2026-98399?
CVE-2026-98399 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-98399?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98399?
CVE-2026-98399 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98399?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-wvr7-cc68-fmx4",
  "modified" : "2026-10-14T15:32:19Z",
  "published" : "2026-10-14T15:32:19Z",
  "aliases" : [ "CVE-2026-98399" ],
  "details" : "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.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98399"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/280ff19853440d59e031cd8fe161e81305721262"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/37f61b71cbc0caefc01022a19ee56fc2510e2e6e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/41647864e62b28388ecccc23a82f0e0a091f4ef2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8d7988e8116c3d29d9e02ca9d37ee84577643f2d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/aed56fa3108b7095e6a048e134981506c056a6cb"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-14T14:17:50Z"
  }
}