<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 30 Sep 2026 03:09:10 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89478 — sctp: drop a chunk if its transport was removed</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89478</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sctp: drop a chunk if its transport was removed&lt;/p&gt;
&lt;p&gt;sctp_rcv() resolves the transport once per packet and leaves it in
chunk-&amp;gt;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.&lt;/p&gt;
&lt;p&gt;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().&lt;/p&gt;
&lt;p&gt;The DATA chunk in that packet puts the removed transport back into
asoc-&amp;gt;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&amp;#39;s state.&lt;/p&gt;
&lt;p&gt;Drop the chunk in sctp_inq_push(), next to the existing rcvr-&amp;gt;dead check.
Both paths reach it with the association&amp;#39;s socket lock held. The peer
retransmits it.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sctp: drop a chunk if its transport was removed&lt;/p&gt;
&lt;p&gt;sctp_rcv() resolves the transport once per packet and leaves it in
chunk-&amp;gt;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.&lt;/p&gt;
&lt;p&gt;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().&lt;/p&gt;
&lt;p&gt;The DATA chunk in that packet puts the removed transport back into
asoc-&amp;gt;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&amp;#39;s state.&lt;/p&gt;
&lt;p&gt;Drop the chunk in sctp_inq_push(), next to the existing rcvr-&amp;gt;dead check.
Both paths reach it with the association&amp;#39;s socket lock held. The peer
retransmits it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89478</guid>
    </item>
  </channel>
</rss>
