CVE-2026-89478

CVE CVE-2026-89478EUVD EUVD-2026-76384Published 2026-09-11T19:43:34.000ZLast changed 2026-09-14T12:00:14.000ZCVSS 9.8

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: sctp: drop a chunk if its transport was removed sctp_rcv() resolves the transport once per packet and leaves it in chunk->transport. The lookup reference, or the one sctp_add_backlog() takes if the socket is owned by userspace, keeps it around until the chunk has been processed. An authenticated ASCONF DEL-IP can remove it in the meantime. sctp_assoc_rm_peer() takes the transport out of the association and calls sctp_transport_free(), which tags it dead and drops the reference the association held. There is a window on both paths: the packet can sit on the socket backlog, and on the direct path the lookup completes before bh_lock_sock(). The DATA chunk in that packet puts the removed transport back into asoc->peer.last_data_from. Once the packet is done that reference goes away and the transport is freed by RCU, so the next delayed SACK carries the pointer into the SACK chunk and sctp_outq_select_transport() reads the freed transport's state. Drop the chunk in sctp_inq_push(), next to the existing rcvr->dead check. Both paths reach it with the association's socket lock held. The peer retransmits it.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1035bdef1efb9b1076d1a57b81e08c637ff08ecc; patch: 6.1.188; 2.6.12; patch: 6.12.109; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3fc072e7cb4a0ff251d13cfc2d24f62489cd9386; patch: 7.2.4; patch: 5.15.221; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d7cb5ad832095dc4becfdb2a36007ffd50e49fb0; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c6c86a5e62a4fec36692ddd64b9144b660f71f96; patch: 7.3-rc1; patch: 6.6.157; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <03a9d10ecf71f54b2af8020935f2033d4a132be5; patch: 0; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <928fd7920ba37cc5637a211b9be979083413a2fa; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0422b092a3d43ca462932ff9f747731ca078d1d4; patch: 6.18.50; patch: 5.10.270; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3537961df2163258bddc230db0e18dc14e925ea6

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.