<?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>Fri, 02 Oct 2026 15:42:43 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43502 — net/rds: handle zerocopy send cleanup before the message is queued</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43502</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;net/rds: handle zerocopy send cleanup before the message is queued&lt;/p&gt;
&lt;p&gt;A zerocopy send can fail after user pages have been pinned but before
the message is attached to the sending socket.&lt;/p&gt;
&lt;p&gt;The purge path currently infers zerocopy state from rm-&amp;gt;m_rs, so an
unqueued message can be cleaned up as if it owned normal payload pages.
However, zerocopy ownership is really determined by the presence of
op_mmp_znotifier, regardless of whether the message has reached the
socket queue.&lt;/p&gt;
&lt;p&gt;Capture op_mmp_znotifier up front in rds_message_purge() and use it as
the cleanup discriminator. If the message is already associated with a
socket, keep the existing completion path. Otherwise, drop the pinned
page accounting directly and release the notifier before putting the
payload pages.&lt;/p&gt;
&lt;p&gt;This keeps early send failure cleanup consistent with the zerocopy
lifetime rules without changing the normal queued completion path.&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;net/rds: handle zerocopy send cleanup before the message is queued&lt;/p&gt;
&lt;p&gt;A zerocopy send can fail after user pages have been pinned but before
the message is attached to the sending socket.&lt;/p&gt;
&lt;p&gt;The purge path currently infers zerocopy state from rm-&amp;gt;m_rs, so an
unqueued message can be cleaned up as if it owned normal payload pages.
However, zerocopy ownership is really determined by the presence of
op_mmp_znotifier, regardless of whether the message has reached the
socket queue.&lt;/p&gt;
&lt;p&gt;Capture op_mmp_znotifier up front in rds_message_purge() and use it as
the cleanup discriminator. If the message is already associated with a
socket, keep the existing completion path. Otherwise, drop the pinned
page accounting directly and release the notifier before putting the
payload pages.&lt;/p&gt;
&lt;p&gt;This keeps early send failure cleanup consistent with the zerocopy
lifetime rules without changing the normal queued completion path.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43502</guid>
    </item>
  </channel>
</rss>
