CVE-2026-98123
CVE.org · Published
- Record status
- Published
- Identifier year (not publication year)
- 2026
- Source publication
- Source updated
- Imported by cveboard
- Source snapshot
- cve_2026-10-24_midnight_baseline ·
CNA source text (English)
sctp: fix soft lockup from unpadded ASCONF-ACK parameter iteration
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.
Scoped product and version facts
Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.
Exploitation unknown; this catalogue does not assess exploitation.
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
unaffected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | affected | git | ba54cad229977f4fae6355dbdaf117088414fdd0 | Unavailable | None listed |
| 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | affected | git | 7d8e7ab6a0665888beee91f7ad77ac805963c4fd | Unavailable | None listed |
| 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | affected | git | 5fbc6a778d5fce7628821236972596acb18e1065 | Unavailable | None listed |
| 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | affected | git | 4548d843e7b29f6d150d8caae4e64015fa226b0c | Unavailable | None listed |
| 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | affected | git | abf59d7f6fff23227256e8199aca5ade45758f8b | Unavailable | None listed |
| 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | affected | git | 3be02999ab9131a4b96eb1eda4ca48b1cea80f03 | Unavailable | None listed |
| 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | affected | git | 7ba84e2971d208a2d6413a334ec28a8a32cdce0f | Unavailable | None listed |
| 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 | affected | git | 2cb0b0b1ed69430bf73740377ea0a1c44c50db63 | Unavailable | None listed |
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
affected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 2.6.12 | affected | Unavailable | Unavailable | Unavailable | None listed |
| 0 | unaffected | semver | 2.6.12 | Unavailable | None listed |
| 5.10.271 | unaffected | semver | Unavailable | 5.10.* | None listed |
| 5.15.222 | unaffected | semver | Unavailable | 5.15.* | None listed |
| 6.1.189 | unaffected | semver | Unavailable | 6.1.* | None listed |
| 6.6.158 | unaffected | semver | Unavailable | 6.6.* | None listed |
| 6.12.111 | unaffected | semver | Unavailable | 6.12.* | None listed |
| 6.18.53 | unaffected | semver | Unavailable | 6.18.* | None listed |
| 7.2.7 | unaffected | semver | Unavailable | 7.2.* | None listed |
| 7.3 | unaffected | original_commit_for_fix | Unavailable | * | None listed |