CVE-2026-98123: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-f2r5-8634-vv9q
Share
Published
Advisory Summary

CVE-2026-98123 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-98123 at a Glance

CVE Identifier CVE-2026-98123
GHSA Identifier GHSA-f2r5-8634-vv9q
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-98123

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-98123, 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: sctp: fix soft lockup from unpadded ASCONF-ACK parameter iteration sctp_verify_asconf() walks ASCONF-ACK parameters with sctp_walk_params(), which advances by SCTP_PAD4(length), while the consumer sctp_get_asconf_response() iterates the same parameters advancing by the raw length, without padding. A single odd-length parameter desynchronises the two walks and makes the consumer interpret attacker-controlled bytes at a misaligned offset. When those bytes yield a length of zero, the while loop over asconf_ack_len makes no progress, spinning forever in softirq context, and the watchdog reports a soft lockup. All reads stay within the received skb, so the lockup is a pure remote denial of service. A remote peer can trigger it with a crafted ASCONF-ACK on an ADD-IP enabled association with an outstanding ASCONF (RFC 5061 section 4.1.2 requires the chunk to be authenticated, but the predefined empty key id 0 allows the peer to compute the same association HMAC from publicly exchanged parameters, so the gate does not help). The SCTP_PARAM_ERR_CAUSE case of sctp_verify_asconf() also performs no length check, letting a parameter without a complete error header reach the consumer, which reads errhdr.cause past the end of the parameter, an out-of-bounds read. Reject SCTP_PARAM_ERR_CAUSE parameters shorter than sizeof(struct sctp_addip_param) + sizeof(struct sctp_errhdr) at the verifier, and advance the consumer iterator with the same padding rule as the verifier to keep the two walks in lockstep. The verifier change guarantees a complete error header in every ERR_CAUSE parameter the consumer can see, so the consumer's asconf_ack_len check is dropped and it returns err_param->cause directly. The consumer padding fix is still required because odd lengths remain valid for SCTP_PARAM_ERR_CAUSE per RFC 5061. The issue was found by ZeroHive, a vulnerability hunting agent at Tencent Yunding Lab.

References

NVD — CVE-2026-98123 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98123
git.kernel.org/stable/c/2cb0b0b1ed... WEB
https://git.kernel.org/stable/c/2cb0b0b1ed69430bf73740377ea0a1c44c50db63
git.kernel.org/stable/c/3be02999ab... WEB
https://git.kernel.org/stable/c/3be02999ab9131a4b96eb1eda4ca48b1cea80f03
git.kernel.org/stable/c/4548d843e7... WEB
https://git.kernel.org/stable/c/4548d843e7b29f6d150d8caae4e64015fa226b0c
git.kernel.org/stable/c/5fbc6a778d... WEB
https://git.kernel.org/stable/c/5fbc6a778d5fce7628821236972596acb18e1065
git.kernel.org/stable/c/7ba84e2971... WEB
https://git.kernel.org/stable/c/7ba84e2971d208a2d6413a334ec28a8a32cdce0f
git.kernel.org/stable/c/7d8e7ab6a0... WEB
https://git.kernel.org/stable/c/7d8e7ab6a0665888beee91f7ad77ac805963c4fd
git.kernel.org/stable/c/abf59d7f6f... WEB
https://git.kernel.org/stable/c/abf59d7f6fff23227256e8199aca5ade45758f8b
git.kernel.org/stable/c/ba54cad229... WEB
https://git.kernel.org/stable/c/ba54cad229977f4fae6355dbdaf117088414fdd0

Frequently Asked Questions

What is CVE-2026-98123?
CVE-2026-98123 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-98123?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98123?
CVE-2026-98123 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98123?
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-f2r5-8634-vv9q",
  "modified" : "2026-10-03T12:31:28Z",
  "published" : "2026-09-25T12:31:37Z",
  "aliases" : [ "CVE-2026-98123" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nsctp: fix soft lockup from unpadded ASCONF-ACK parameter iteration\n\nsctp_verify_asconf() walks ASCONF-ACK parameters with\nsctp_walk_params(), which advances by SCTP_PAD4(length), while the\nconsumer sctp_get_asconf_response() iterates the same parameters\nadvancing by the raw length, without padding. A single odd-length\nparameter desynchronises the two walks and makes the consumer\ninterpret attacker-controlled bytes at a misaligned offset.\n\nWhen those bytes yield a length of zero, the while loop over\nasconf_ack_len makes no progress, spinning forever in softirq\ncontext, and the watchdog reports a soft lockup. All reads stay\nwithin the received skb, so the lockup is a pure remote denial of\nservice. A remote peer can trigger it with a crafted ASCONF-ACK on\nan ADD-IP enabled association with an outstanding ASCONF (RFC 5061\nsection 4.1.2 requires the chunk to be authenticated, but the\npredefined empty key id 0 allows the peer to compute the same\nassociation HMAC from publicly exchanged parameters, so the gate\ndoes not help).\n\nThe SCTP_PARAM_ERR_CAUSE case of sctp_verify_asconf() also performs\nno length check, letting a parameter without a complete error\nheader reach the consumer, which reads errhdr.cause past the end of\nthe parameter, an out-of-bounds read.\n\nReject SCTP_PARAM_ERR_CAUSE parameters shorter than\nsizeof(struct sctp_addip_param) + sizeof(struct sctp_errhdr) at the\nverifier, and advance the consumer iterator with the same padding\nrule as the verifier to keep the two walks in lockstep. The verifier\nchange guarantees a complete error header in every ERR_CAUSE\nparameter the consumer can see, so the consumer's asconf_ack_len\ncheck is dropped and it returns err_param->cause directly. The\nconsumer padding fix is still required because odd lengths remain\nvalid for SCTP_PARAM_ERR_CAUSE per RFC 5061.\n\nThe issue was found by ZeroHive, a vulnerability hunting agent at\nTencent Yunding Lab.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98123"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2cb0b0b1ed69430bf73740377ea0a1c44c50db63"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/3be02999ab9131a4b96eb1eda4ca48b1cea80f03"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4548d843e7b29f6d150d8caae4e64015fa226b0c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5fbc6a778d5fce7628821236972596acb18e1065"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7ba84e2971d208a2d6413a334ec28a8a32cdce0f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7d8e7ab6a0665888beee91f7ad77ac805963c4fd"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/abf59d7f6fff23227256e8199aca5ade45758f8b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ba54cad229977f4fae6355dbdaf117088414fdd0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-25T11:17:43Z"
  }
}