CVE-2026-89477
Last modified
CVE-2026-89477 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: sctp: fix NULL deref on untransmitted RECONF completion sctp_process_strreset_outreq(), sctp_process_strreset_addstrm_out() and sctp_process_strreset_resp() complete a pending stream reconfiguration request by stopping the reconf timer on the transport it was sent on: t = asoc->strreset_chunk->transport; if (timer_delete(&t->reconf_timer)) sctp_transport_put(t); chunk->transport is assigned by __sctp_packet_append_chunk() when the chunk is appended to an outbound packet, and sctp_outq_flush_ctrl() arms the reconf timer at that same point. A request already published in asoc->strreset_chunk but not yet transmitted has neither, so completing it dereferences NULL. Two ways to get there. EPSS estimates a 0.45% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: sctp: fix NULL deref on untransmitted RECONF completion sctp_process_strreset_outreq(), sctp_process_strreset_addstrm_out() and sctp_process_strreset_resp() complete a pending stream reconfiguration request by stopping the reconf timer on the transport it was sent on: t = asoc->strreset_chunk->transport; if (timer_delete(&t->reconf_timer)) sctp_transport_put(t); chunk->transport is assigned by __sctp_packet_append_chunk() when the chunk is appended to an outbound packet, and sctp_outq_flush_ctrl() arms the reconf timer at that same point. A request already published in asoc->strreset_chunk but not yet transmitted has neither, so completing it dereferences NULL. Two ways to get there. sctp_send_asconf_del_ip() sets asoc->src_out_of_asoc_ok without sending anything when the address being removed is the association's last one, and sctp_outq_flush_ctrl() then leaves every non-ASCONF control chunk queued; as only sctp_process_asconf_ack() clears that flag, it persists. An unprivileged process that removes such an address and then asks for a stream reset panics the kernel from softirq. A peer needs neither ASCONF nor local help: sctp_cmd_interpreter() uncorks the outqueue only once the whole packet has been processed, so a reply built while walking a RECONF chunk stays untransmitted for the rest of that walk, and one RECONF chunk carrying [Incoming SSN Reset Request, Outgoing SSN Reset Request, Response] -- or two RECONF chunks in one packet -- reaches the same dereference. KASAN: null-ptr-deref in range [0x00000000000001e8-0x00000000000001ef] RIP: 0010:timer_delete+0x67/0x110 Call Trace: <IRQ> sctp_process_strreset_addstrm_out (net/sctp/stream.c:832) sctp_sf_do_reconf (net/sctp/sm_statefuns.c:4212) sctp_do_sm (net/sctp/sm_sideeffect.c:1172) sctp_assoc_bh_rcv (net/sctp/associola.c:1044) sctp_rcv (net/sctp/input.c:243) ip_local_deliver (net/ipv4/ip_input.c:262) process_backlog (net/core/dev.c:6680) </IRQ> A response can only acknowledge a request that was actually sent, so do not match asoc->strreset_chunk while chunk->transport is NULL. Guarding the lookup covers all three completion sites.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 81054476453640159149cb6704e834893e16736b, < 79ff751311e80fa0370007e46a79a6d601685e75; >= 81054476453640159149cb6704e834893e16736b, < 53141db979687eae7dc6d29414cefc77034f967e; >= 81054476453640159149cb6704e834893e16736b, < 68891125af5a5dfbca728809a16637a869bbe0df; >= 81054476453640159149cb6704e834893e16736b, < b2d6d873b4dfb5b84194061c4b40a1cd85b92ca4; >= 81054476453640159149cb6704e834893e16736b, < 77ea60f2d24002c308f224db44a4542c466489af; >= 81054476453640159149cb6704e834893e16736b, < 25419f516ea84b1e7d3d55aae5215ac86ece0c66; >= 81054476453640159149cb6704e834893e16736b, < 0ee697defc0594f1da810ed75d9d643fb46f5318; >= 81054476453640159149cb6704e834893e16736b, < 2db9bfa3e27bdea15e05ea70b56bad3d21e570ec |
| Linux | Linux | 4.11 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-89477?
How severe is CVE-2026-89477?
How do I fix CVE-2026-89477?
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-89471In the Linux kernel, the following vulnerability has been re…8.4
- CVE-2026-89472In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-89473In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89474In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89475In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89476In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-89478In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-89479In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-8948Same-origin policy bypass in the DOM: Networking component. …9.1
- CVE-2026-89480In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-89481In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-89482In the Linux kernel, the following vulnerability has been re…9.8
Are you affected by CVE-2026-89477?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
