<?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 00:50:09 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-47024 — vsock/virtio: free queued packets when closing socket</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2021-47024</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;vsock/virtio: free queued packets when closing socket&lt;/p&gt;
&lt;p&gt;As reported by syzbot [1], there is a memory leak while closing the
socket. We partially solved this issue with commit ac03046ece2b
(&amp;#34;vsock/virtio: free packets during the socket release&amp;#34;), but we
forgot to drain the RX queue when the socket is definitely closed by
the scheduled work.&lt;/p&gt;
&lt;p&gt;To avoid future issues, let&amp;#39;s use the new virtio_transport_remove_sock()
to drain the RX queue before removing the socket from the af_vsock lists
calling vsock_remove_sock().&lt;/p&gt;
&lt;p&gt;[1] https://syzkaller.appspot.com/bug?extid=24452624fc4c571eedd9&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;vsock/virtio: free queued packets when closing socket&lt;/p&gt;
&lt;p&gt;As reported by syzbot [1], there is a memory leak while closing the
socket. We partially solved this issue with commit ac03046ece2b
(&amp;#34;vsock/virtio: free packets during the socket release&amp;#34;), but we
forgot to drain the RX queue when the socket is definitely closed by
the scheduled work.&lt;/p&gt;
&lt;p&gt;To avoid future issues, let&amp;#39;s use the new virtio_transport_remove_sock()
to drain the RX queue before removing the socket from the af_vsock lists
calling vsock_remove_sock().&lt;/p&gt;
&lt;p&gt;[1] https://syzkaller.appspot.com/bug?extid=24452624fc4c571eedd9&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2021-47024</guid>
    </item>
  </channel>
</rss>
