CVE-2026-98123sctp: fix soft lockup from unpadded ASCONF-ACK parameter iteration
- 5.5MediumCVSS base score
- 0.10%Exploitation in 30 daysEPSS · top 99% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
Published
- 24 days later
· 24 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.10% · top 99% of all CVEs (18 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < ba54cad229977f4fae6355dbdaf117088414fdd0
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 7d8e7ab6a0665888beee91f7ad77ac805963c4fd
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 5fbc6a778d5fce7628821236972596acb18e1065
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 4548d843e7b29f6d150d8caae4e64015fa226b0c
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < abf59d7f6fff23227256e8199aca5ade45758f8b
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 3be02999ab9131a4b96eb1eda4ca48b1cea80f03
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 7ba84e2971d208a2d6413a334ec28a8a32cdce0f
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2cb0b0b1ed69430bf73740377ea0a1c44c50db63
- affected 2.6.12
- unaffected < 2.6.12
- unaffected 5.10.271 – ≤ 5.10.*
- unaffected 5.15.222 – ≤ 5.15.*
- unaffected 6.1.189 – ≤ 6.1.*
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.111 – ≤ 6.12.*
- unaffected 6.18.53 – ≤ 6.18.*
- unaffected 7.2.7 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References8
- https://git.kernel.org/stable/c/ba54cad229977f4fae6355dbdaf117088414fdd0 (opens in a new tab)
- https://git.kernel.org/stable/c/7d8e7ab6a0665888beee91f7ad77ac805963c4fd (opens in a new tab)
- https://git.kernel.org/stable/c/5fbc6a778d5fce7628821236972596acb18e1065 (opens in a new tab)
- https://git.kernel.org/stable/c/4548d843e7b29f6d150d8caae4e64015fa226b0c (opens in a new tab)
- https://git.kernel.org/stable/c/abf59d7f6fff23227256e8199aca5ade45758f8b (opens in a new tab)
- https://git.kernel.org/stable/c/3be02999ab9131a4b96eb1eda4ca48b1cea80f03 (opens in a new tab)
- https://git.kernel.org/stable/c/7ba84e2971d208a2d6413a334ec28a8a32cdce0f (opens in a new tab)
- https://git.kernel.org/stable/c/2cb0b0b1ed69430bf73740377ea0a1c44c50db63 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86954 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98123)Record last updated .