FKIE_CVE-2026-98123

Vulnerability from fkie_nvd - Published: 2026-09-25 11:17 - Updated: 2026-09-25 11:17
Severity
Summary
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
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/2cb0b0b1ed69430bf73740377ea0a1c44c50db63
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/3be02999ab9131a4b96eb1eda4ca48b1cea80f03
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/7ba84e2971d208a2d6413a334ec28a8a32cdce0f
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/abf59d7f6fff23227256e8199aca5ade45758f8b
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "net/sctp/sm_make_chunk.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "abf59d7f6fff23227256e8199aca5ade45758f8b",
              "status": "affected",
              "version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
              "versionType": "git"
            },
            {
              "lessThan": "3be02999ab9131a4b96eb1eda4ca48b1cea80f03",
              "status": "affected",
              "version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
              "versionType": "git"
            },
            {
              "lessThan": "7ba84e2971d208a2d6413a334ec28a8a32cdce0f",
              "status": "affected",
              "version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
              "versionType": "git"
            },
            {
              "lessThan": "2cb0b0b1ed69430bf73740377ea0a1c44c50db63",
              "status": "affected",
              "version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "net/sctp/sm_make_chunk.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "2.6.12"
            },
            {
              "lessThan": "2.6.12",
              "status": "unaffected",
              "version": "0",
              "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-rc2",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "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\u0027s asconf_ack_len\ncheck is dropped and it returns err_param-\u003ecause 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."
    }
  ],
  "id": "CVE-2026-98123",
  "lastModified": "2026-09-25T11:17:43.600",
  "metrics": {},
  "published": "2026-09-25T11:17:43.600",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/2cb0b0b1ed69430bf73740377ea0a1c44c50db63"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/3be02999ab9131a4b96eb1eda4ca48b1cea80f03"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/7ba84e2971d208a2d6413a334ec28a8a32cdce0f"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/abf59d7f6fff23227256e8199aca5ade45758f8b"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Received"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.