<?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>Wed, 30 Sep 2026 17:37:13 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90051 — tcp: reject non zerocopy devmem tx</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-90051</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;tcp: reject non zerocopy devmem tx&lt;/p&gt;
&lt;p&gt;Devmem tcp tx doesn&amp;#39;t work without zero-copy, however it&amp;#39;s not currently
enforced if NETIF_F_SG isn&amp;#39;t present. In this case, tcp_sendmsg_locked()
will try the copy path and try to copy data from an iovec which consists
of offsets into the dma-buf and would normally fail. Moreover,
d9c56501c72fd (&amp;#34;net: tcp: block mixing readable and unreadable frags&amp;#34;)
relies on that and assumes that the devmem binding is present IFF we&amp;#39;re
using the zero-copy path, which can be used to mix net-iov and pages in
a single skb, and break invariants. Let&amp;#39;s reject devmem tx without
zero-copy.&lt;/p&gt;
&lt;p&gt;Note, the parameter check the patch is modifying is too loose, we can
create an io_uring request with dmabuf_id and all ZC flags, but which
won&amp;#39;t have the binding. We replace it with stricter validation.&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;tcp: reject non zerocopy devmem tx&lt;/p&gt;
&lt;p&gt;Devmem tcp tx doesn&amp;#39;t work without zero-copy, however it&amp;#39;s not currently
enforced if NETIF_F_SG isn&amp;#39;t present. In this case, tcp_sendmsg_locked()
will try the copy path and try to copy data from an iovec which consists
of offsets into the dma-buf and would normally fail. Moreover,
d9c56501c72fd (&amp;#34;net: tcp: block mixing readable and unreadable frags&amp;#34;)
relies on that and assumes that the devmem binding is present IFF we&amp;#39;re
using the zero-copy path, which can be used to mix net-iov and pages in
a single skb, and break invariants. Let&amp;#39;s reject devmem tx without
zero-copy.&lt;/p&gt;
&lt;p&gt;Note, the parameter check the patch is modifying is too loose, we can
create an io_uring request with dmabuf_id and all ZC flags, but which
won&amp;#39;t have the binding. We replace it with stricter validation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-90051</guid>
    </item>
  </channel>
</rss>
