<?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 07:31:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74287 — sctp: validate embedded address parameter length</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74287</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: validate embedded address parameter length&lt;/p&gt;
&lt;p&gt;sctp_verify_asconf() and sctp_verify_param() only validate ADD_IP, DEL_IP,
and SET_PRIMARY parameters against a fixed minimum size of sizeof(struct
sctp_addip_param) + sizeof(struct sctp_paramhdr). This ensures the outer
parameter is large enough to contain an embedded address parameter header,
but does not verify that the embedded address parameter&amp;#39;s declared length
fits within the bounds of the outer parameter.&lt;/p&gt;
&lt;p&gt;Later, sctp_process_param() and sctp_process_asconf_param() extract the
embedded address parameter and pass it to af-&amp;gt;from_addr_param(), which uses
the address parameter length to parse the variable-length address payload.
A malformed peer can therefore advertise an embedded address parameter
length that exceeds the remaining bytes in the enclosing parameter.&lt;/p&gt;
&lt;p&gt;Validate that addr_param-&amp;gt;p.length does not exceed the space available
after the sctp_addip_param header before processing the embedded address
parameter. Reject malformed parameters when the embedded address length
extends beyond the enclosing parameter bounds.&lt;/p&gt;
&lt;p&gt;This prevents out-of-bounds reads when parsing malformed parameters carried
in INIT or ASCONF processing paths.&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: validate embedded address parameter length&lt;/p&gt;
&lt;p&gt;sctp_verify_asconf() and sctp_verify_param() only validate ADD_IP, DEL_IP,
and SET_PRIMARY parameters against a fixed minimum size of sizeof(struct
sctp_addip_param) + sizeof(struct sctp_paramhdr). This ensures the outer
parameter is large enough to contain an embedded address parameter header,
but does not verify that the embedded address parameter&amp;#39;s declared length
fits within the bounds of the outer parameter.&lt;/p&gt;
&lt;p&gt;Later, sctp_process_param() and sctp_process_asconf_param() extract the
embedded address parameter and pass it to af-&amp;gt;from_addr_param(), which uses
the address parameter length to parse the variable-length address payload.
A malformed peer can therefore advertise an embedded address parameter
length that exceeds the remaining bytes in the enclosing parameter.&lt;/p&gt;
&lt;p&gt;Validate that addr_param-&amp;gt;p.length does not exceed the space available
after the sctp_addip_param header before processing the embedded address
parameter. Reject malformed parameters when the embedded address length
extends beyond the enclosing parameter bounds.&lt;/p&gt;
&lt;p&gt;This prevents out-of-bounds reads when parsing malformed parameters carried
in INIT or ASCONF processing paths.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74287</guid>
    </item>
  </channel>
</rss>
