Answer in brief
CVE-2026-89477 records a High severity (CVSS 7.5) vulnerability in sctp: fix NULL deref on untransmitted RECONF completion. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=81054476453640159149cb6704e834893e16736b <77ea60f2d24002c308f224db44a4542c466489af || >=81054476453640159149cb6704e834893e16736b <25419f516ea84b1e7d3d55aae5215ac86ece0c66 || >=81054476453640159149cb6704e834893e16736b <0ee697defc0594f1da810ed75d9d643fb46f5318 || >=81054476453640159149cb6704e834893e16736b <2db9bfa3e27bdea15e05ea70b56bad3d21e570ec | 77ea60f2d24002c308f224db44a4542c466489af, 25419f516ea84b1e7d3d55aae5215ac86ece0c66, 0ee697defc0594f1da810ed75d9d643fb46f5318, 2db9bfa3e27bdea15e05ea70b56bad3d21e570ec |
| Linux/Linuxgeneric | 4.11 | Not reported |
| Linux/Linuxgeneric | >=81054476453640159149cb6704e834893e16736b <79ff751311e80fa0370007e46a79a6d601685e75 || >=81054476453640159149cb6704e834893e16736b <53141db979687eae7dc6d29414cefc77034f967e || >=81054476453640159149cb6704e834893e16736b <68891125af5a5dfbca728809a16637a869bbe0df || >=81054476453640159149cb6704e834893e16736b <b2d6d873b4dfb5b84194061c4b40a1cd85b92ca4 || >=81054476453640159149cb6704e834893e16736b <77ea60f2d24002c308f224db44a4542c466489af || >=81054476453640159149cb6704e834893e16736b <25419f516ea84b1e7d3d55aae5215ac86ece0c66 || >=81054476453640159149cb6704e834893e16736b <0ee697defc0594f1da810ed75d9d643fb46f5318 || >=81054476453640159149cb6704e834893e16736b <2db9bfa3e27bdea15e05ea70b56bad3d21e570ec | 79ff751311e80fa0370007e46a79a6d601685e75, 53141db979687eae7dc6d29414cefc77034f967e, 68891125af5a5dfbca728809a16637a869bbe0df, b2d6d873b4dfb5b84194061c4b40a1cd85b92ca4, 77ea60f2d24002c308f224db44a4542c466489af, 25419f516ea84b1e7d3d55aae5215ac86ece0c66, 0ee697defc0594f1da810ed75d9d643fb46f5318, 2db9bfa3e27bdea15e05ea70b56bad3d21e570ec |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.