<?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://cve.radiocsirt.org</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, 06 Oct 2026 07:17:20 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-48819 — tcp: take care of mixed splice()/sendmsg(MSG_ZEROCOPY) case</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-48819</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: take care of mixed splice()/sendmsg(MSG_ZEROCOPY) case&lt;/p&gt;
&lt;p&gt;syzbot found that mixing sendpage() and sendmsg(MSG_ZEROCOPY)
calls over the same TCP socket would again trigger the
infamous warning in inet_sock_destruct()&lt;/p&gt;
&lt;p&gt;WARN_ON(sk_forward_alloc_get(sk));&lt;/p&gt;
&lt;p&gt;While Talal took into account a mix of regular copied data
and MSG_ZEROCOPY one in the same skb, the sendpage() path
has been forgotten.&lt;/p&gt;
&lt;p&gt;We want the charging to happen for sendpage(), because
pages could be coming from a pipe. What is missing is the
downgrading of pure zerocopy status to make sure
sk_forward_alloc will stay synced.&lt;/p&gt;
&lt;p&gt;Add tcp_downgrade_zcopy_pure() helper so that we can
use it from the two callers.&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: take care of mixed splice()/sendmsg(MSG_ZEROCOPY) case&lt;/p&gt;
&lt;p&gt;syzbot found that mixing sendpage() and sendmsg(MSG_ZEROCOPY)
calls over the same TCP socket would again trigger the
infamous warning in inet_sock_destruct()&lt;/p&gt;
&lt;p&gt;WARN_ON(sk_forward_alloc_get(sk));&lt;/p&gt;
&lt;p&gt;While Talal took into account a mix of regular copied data
and MSG_ZEROCOPY one in the same skb, the sendpage() path
has been forgotten.&lt;/p&gt;
&lt;p&gt;We want the charging to happen for sendpage(), because
pages could be coming from a pipe. What is missing is the
downgrading of pure zerocopy status to make sure
sk_forward_alloc will stay synced.&lt;/p&gt;
&lt;p&gt;Add tcp_downgrade_zcopy_pure() helper so that we can
use it from the two callers.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-48819</guid>
    </item>
  </channel>
</rss>
