<?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>Tue, 29 Sep 2026 15:58:09 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-52924 — sctp: purge outqueue on stale COOKIE-ECHO handling</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-52924</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sctp: purge outqueue on stale COOKIE-ECHO handling&lt;/p&gt;
&lt;p&gt;sctp_stream_update() is only invoked when the association is moved into
COOKIE_WAIT during association setup/reconfiguration. In this path, the
outbound stream scheduler state (stream-&amp;gt;out_curr) is expected to be
clean, since no user data should have been transmitted yet unless the
state machine has already partially progressed.&lt;/p&gt;
&lt;p&gt;However, a corner case exists in sctp_sf_do_5_2_6_stale(): when a
Stale Cookie ERROR is received, the association is rolled back from
COOKIE_ECHOED to COOKIE_WAIT. In this scenario, user data may already
have been queued and even bundled with the COOKIE-ECHO chunk.&lt;/p&gt;
&lt;p&gt;During the rollback, sctp_stream_update() frees the old stream table
and installs a new one, but it does not invalidate stream-&amp;gt;out_curr.
As a result, out_curr may still point to a freed sctp_stream_out
entry from the previous stream state.&lt;/p&gt;
&lt;p&gt;Later, SCTP scheduler dequeue paths (FCFS, RR, PRIO, etc.) rely on
stream-&amp;gt;out_curr-&amp;gt;ext, which can lead to use-after-free once the old
stream state has been released via sctp_stream_free().&lt;/p&gt;
&lt;p&gt;This results in crashes such as (reported by Yuqi):&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in sctp_sched_fcfs_dequeue+0x13a/0x140
  Read of size 8 at addr ff1100004d4d3208 by task mini_poc/9312
  CPU: 1 UID: 1001 PID: 9312 Comm: mini_poc Not tainted
     7.1.0-rc1-00305-gbd3a4795d574 #5 PREEMPT(full)
   sctp_sched_fcfs_dequeue+0x13a/0x140
   sctp_…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sctp: purge outqueue on stale COOKIE-ECHO handling&lt;/p&gt;
&lt;p&gt;sctp_stream_update() is only invoked when the association is moved into
COOKIE_WAIT during association setup/reconfiguration. In this path, the
outbound stream scheduler state (stream-&amp;gt;out_curr) is expected to be
clean, since no user data should have been transmitted yet unless the
state machine has already partially progressed.&lt;/p&gt;
&lt;p&gt;However, a corner case exists in sctp_sf_do_5_2_6_stale(): when a
Stale Cookie ERROR is received, the association is rolled back from
COOKIE_ECHOED to COOKIE_WAIT. In this scenario, user data may already
have been queued and even bundled with the COOKIE-ECHO chunk.&lt;/p&gt;
&lt;p&gt;During the rollback, sctp_stream_update() frees the old stream table
and installs a new one, but it does not invalidate stream-&amp;gt;out_curr.
As a result, out_curr may still point to a freed sctp_stream_out
entry from the previous stream state.&lt;/p&gt;
&lt;p&gt;Later, SCTP scheduler dequeue paths (FCFS, RR, PRIO, etc.) rely on
stream-&amp;gt;out_curr-&amp;gt;ext, which can lead to use-after-free once the old
stream state has been released via sctp_stream_free().&lt;/p&gt;
&lt;p&gt;This results in crashes such as (reported by Yuqi):&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in sctp_sched_fcfs_dequeue+0x13a/0x140
  Read of size 8 at addr ff1100004d4d3208 by task mini_poc/9312
  CPU: 1 UID: 1001 PID: 9312 Comm: mini_poc Not tainted
     7.1.0-rc1-00305-gbd3a4795d574 #5 PREEMPT(full)
   sctp_sched_fcfs_dequeue+0x13a/0x140
   sctp_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-52924</guid>
    </item>
  </channel>
</rss>
