<?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>Mon, 28 Sep 2026 10:54:39 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-40281 — sctp: prevent possible shift-out-of-bounds in sctp_transport_update_rto</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-40281</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens RUGGEDCOM RST2428P&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sctp: prevent possible shift-out-of-bounds in sctp_transport_update_rto&lt;/p&gt;
&lt;p&gt;syzbot reported a possible shift-out-of-bounds [1]&lt;/p&gt;
&lt;p&gt;Blamed commit added rto_alpha_max and rto_beta_max set to 1000.&lt;/p&gt;
&lt;p&gt;It is unclear if some sctp users are setting very large rto_alpha
and/or rto_beta.&lt;/p&gt;
&lt;p&gt;In order to prevent user regression, perform the test at run time.&lt;/p&gt;
&lt;p&gt;Also add READ_ONCE() annotations as sysctl values can change under us.&lt;/p&gt;
&lt;p&gt;[1]&lt;/p&gt;
&lt;p&gt;UBSAN: shift-out-of-bounds in net/sctp/transport.c:509:41
shift exponent 64 is too large for 32-bit type &amp;#39;unsigned int&amp;#39;
CPU: 0 UID: 0 PID: 16704 Comm: syz.2.2320 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
 &amp;lt;TASK&amp;gt;
  __dump_stack lib/dump_stack.c:94 [inline]
  dump_stack_lvl+0x16c/0x1f0 lib/dump_stack.c:120
  ubsan_epilogue lib/ubsan.c:233 [inline]
  __ubsan_handle_shift_out_of_bounds+0x27f/0x420 lib/ubsan.c:494
  sctp_transport_update_rto.cold+0x1c/0x34b net/sctp/transport.c:509
  sctp_check_transmitted+0x11c4/0x1c30 net/sctp/outqueue.c:1502
  sctp_outq_sack+0x4ef/0x1b20 net/sctp/outqueue.c:1338
  sctp_cmd_process_sack net/sctp/sm_sideeffect.c:840 [inline]
  sctp_cmd_interpreter net/sctp/sm_sideeffect.c:1372 [inline]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens RUGGEDCOM RST2428P&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sctp: prevent possible shift-out-of-bounds in sctp_transport_update_rto&lt;/p&gt;
&lt;p&gt;syzbot reported a possible shift-out-of-bounds [1]&lt;/p&gt;
&lt;p&gt;Blamed commit added rto_alpha_max and rto_beta_max set to 1000.&lt;/p&gt;
&lt;p&gt;It is unclear if some sctp users are setting very large rto_alpha
and/or rto_beta.&lt;/p&gt;
&lt;p&gt;In order to prevent user regression, perform the test at run time.&lt;/p&gt;
&lt;p&gt;Also add READ_ONCE() annotations as sysctl values can change under us.&lt;/p&gt;
&lt;p&gt;[1]&lt;/p&gt;
&lt;p&gt;UBSAN: shift-out-of-bounds in net/sctp/transport.c:509:41
shift exponent 64 is too large for 32-bit type &amp;#39;unsigned int&amp;#39;
CPU: 0 UID: 0 PID: 16704 Comm: syz.2.2320 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
 &amp;lt;TASK&amp;gt;
  __dump_stack lib/dump_stack.c:94 [inline]
  dump_stack_lvl+0x16c/0x1f0 lib/dump_stack.c:120
  ubsan_epilogue lib/ubsan.c:233 [inline]
  __ubsan_handle_shift_out_of_bounds+0x27f/0x420 lib/ubsan.c:494
  sctp_transport_update_rto.cold+0x1c/0x34b net/sctp/transport.c:509
  sctp_check_transmitted+0x11c4/0x1c30 net/sctp/outqueue.c:1502
  sctp_outq_sack+0x4ef/0x1b20 net/sctp/outqueue.c:1338
  sctp_cmd_process_sack net/sctp/sm_sideeffect.c:840 [inline]
  sctp_cmd_interpreter net/sctp/sm_sideeffect.c:1372 [inline]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-40281</guid>
    </item>
  </channel>
</rss>
