<?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 11:19:49 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53825 — kcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg().</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53825</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;kcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg().&lt;/p&gt;
&lt;p&gt;syzkaller found a memory leak in kcm_sendmsg(), and commit c821a88bd720
(&amp;#34;kcm: Fix memory leak in error path of kcm_sendmsg()&amp;#34;) suppressed it by
updating kcm_tx_msg(head)-&amp;gt;last_skb if partial data is copied so that the
following sendmsg() will resume from the skb.&lt;/p&gt;
&lt;p&gt;However, we cannot know how many bytes were copied when we get the error.
Thus, we could mess up the MSG_MORE queue.&lt;/p&gt;
&lt;p&gt;When kcm_sendmsg() fails for SOCK_DGRAM, we should purge the queue as we
do so for UDP by udp_flush_pending_frames().&lt;/p&gt;
&lt;p&gt;Even without this change, when the error occurred, the following sendmsg()
resumed from a wrong skb and the queue was messed up.  However, we have
yet to get such a report, and only syzkaller stumbled on it.  So, this
can be changed safely.&lt;/p&gt;
&lt;p&gt;Note this does not change SOCK_SEQPACKET behaviour.&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;kcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg().&lt;/p&gt;
&lt;p&gt;syzkaller found a memory leak in kcm_sendmsg(), and commit c821a88bd720
(&amp;#34;kcm: Fix memory leak in error path of kcm_sendmsg()&amp;#34;) suppressed it by
updating kcm_tx_msg(head)-&amp;gt;last_skb if partial data is copied so that the
following sendmsg() will resume from the skb.&lt;/p&gt;
&lt;p&gt;However, we cannot know how many bytes were copied when we get the error.
Thus, we could mess up the MSG_MORE queue.&lt;/p&gt;
&lt;p&gt;When kcm_sendmsg() fails for SOCK_DGRAM, we should purge the queue as we
do so for UDP by udp_flush_pending_frames().&lt;/p&gt;
&lt;p&gt;Even without this change, when the error occurred, the following sendmsg()
resumed from a wrong skb and the queue was messed up.  However, we have
yet to get such a report, and only syzkaller stumbled on it.  So, this
can be changed safely.&lt;/p&gt;
&lt;p&gt;Note this does not change SOCK_SEQPACKET behaviour.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53825</guid>
    </item>
  </channel>
</rss>
