CVE-2026-98123
Last modified
CVE-2026-98123 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 2.6.12.1, < 5.10.271 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.222 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.189 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.158 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.111 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.53 | — |
| Linux | Linux Kernel | >= 6.19, < 7.2.7 | — |
| Linux | Linux Kernel | 2.6.12 | — |
| Linux | Linux Kernel | 7.3 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-98123?
How severe is CVE-2026-98123?
How do I fix CVE-2026-98123?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-98118In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-98119In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-9812Mattermost versions 11.9.x <= 11.9.0, 11.8.x <= 11.8.4, 11.7…6.5
- CVE-2026-98120In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-98121In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-98122In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-98124In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-98125In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-98126In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-98127In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-98128In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-98129In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-98123?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
