<?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 20:52:42 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-53004 — sctp: fix OOB write to userspace in sctp_getsockopt_peer_auth_chunks</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-53004</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: fix OOB write to userspace in sctp_getsockopt_peer_auth_chunks&lt;/p&gt;
&lt;p&gt;sctp_getsockopt_peer_auth_chunks() checks that the caller&amp;#39;s optval
buffer is large enough for the peer AUTH chunk list with&lt;/p&gt;
&lt;p&gt;if (len &amp;lt; num_chunks)
            return -EINVAL;&lt;/p&gt;
&lt;p&gt;but then writes num_chunks bytes to p-&amp;gt;gauth_chunks, which lives
at offset offsetof(struct sctp_authchunks, gauth_chunks) == 8
inside optval.  The check is missing the sizeof(struct
sctp_authchunks) = 8-byte header.  When the caller supplies
len == num_chunks (for any num_chunks &amp;gt; 0) the test passes but
copy_to_user() writes sizeof(struct sctp_authchunks) = 8 bytes
past the declared buffer.&lt;/p&gt;
&lt;p&gt;The sibling function sctp_getsockopt_local_auth_chunks() at the
next line already has the correct check:&lt;/p&gt;
&lt;p&gt;if (len &amp;lt; sizeof(struct sctp_authchunks) + num_chunks)
            return -EINVAL;&lt;/p&gt;
&lt;p&gt;Align the peer variant with its sibling.&lt;/p&gt;
&lt;p&gt;Reproducer confirms on v7.0-13-generic: an unprivileged userspace
caller that opens a loopback SCTP association with AUTH enabled,
queries num_chunks with a short optval, then issues the real
getsockopt with len == num_chunks and sentinel bytes painted past
the buffer observes those sentinel bytes overwritten with the
peer&amp;#39;s AUTH chunk type.  The bytes written are under the peer&amp;#39;s
control but land in the caller&amp;#39;s own userspace; this is not a
kernel memory corruption, but it is a kernel-side contract
violation that can silently corrupt adjacent…&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: fix OOB write to userspace in sctp_getsockopt_peer_auth_chunks&lt;/p&gt;
&lt;p&gt;sctp_getsockopt_peer_auth_chunks() checks that the caller&amp;#39;s optval
buffer is large enough for the peer AUTH chunk list with&lt;/p&gt;
&lt;p&gt;if (len &amp;lt; num_chunks)
            return -EINVAL;&lt;/p&gt;
&lt;p&gt;but then writes num_chunks bytes to p-&amp;gt;gauth_chunks, which lives
at offset offsetof(struct sctp_authchunks, gauth_chunks) == 8
inside optval.  The check is missing the sizeof(struct
sctp_authchunks) = 8-byte header.  When the caller supplies
len == num_chunks (for any num_chunks &amp;gt; 0) the test passes but
copy_to_user() writes sizeof(struct sctp_authchunks) = 8 bytes
past the declared buffer.&lt;/p&gt;
&lt;p&gt;The sibling function sctp_getsockopt_local_auth_chunks() at the
next line already has the correct check:&lt;/p&gt;
&lt;p&gt;if (len &amp;lt; sizeof(struct sctp_authchunks) + num_chunks)
            return -EINVAL;&lt;/p&gt;
&lt;p&gt;Align the peer variant with its sibling.&lt;/p&gt;
&lt;p&gt;Reproducer confirms on v7.0-13-generic: an unprivileged userspace
caller that opens a loopback SCTP association with AUTH enabled,
queries num_chunks with a short optval, then issues the real
getsockopt with len == num_chunks and sentinel bytes painted past
the buffer observes those sentinel bytes overwritten with the
peer&amp;#39;s AUTH chunk type.  The bytes written are under the peer&amp;#39;s
control but land in the caller&amp;#39;s own userspace; this is not a
kernel memory corruption, but it is a kernel-side contract
violation that can silently corrupt adjacent…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-53004</guid>
    </item>
  </channel>
</rss>
