<?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>Wed, 07 Oct 2026 22:25:07 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-48786 — vsock: remove vsock from connected table when connect is interrupted by a signal</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-48786</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: remove vsock from connected table when connect is interrupted by a signal&lt;/p&gt;
&lt;p&gt;vsock_connect() expects that the socket could already be in the
TCP_ESTABLISHED state when the connecting task wakes up with a signal
pending. If this happens the socket will be in the connected table, and
it is not removed when the socket state is reset. In this situation it&amp;#39;s
common for the process to retry connect(), and if the connection is
successful the socket will be added to the connected table a second
time, corrupting the list.&lt;/p&gt;
&lt;p&gt;Prevent this by calling vsock_remove_connected() if a signal is received
while waiting for a connection. This is harmless if the socket is not in
the connected table, and if it is in the table then removing it will
prevent list corruption from a double add.&lt;/p&gt;
&lt;p&gt;Note for backporting: this patch requires d5afa82c977e (&amp;#34;vsock: correct
removal of socket from the list&amp;#34;), which is in all current stable trees
except 4.9.y.&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: remove vsock from connected table when connect is interrupted by a signal&lt;/p&gt;
&lt;p&gt;vsock_connect() expects that the socket could already be in the
TCP_ESTABLISHED state when the connecting task wakes up with a signal
pending. If this happens the socket will be in the connected table, and
it is not removed when the socket state is reset. In this situation it&amp;#39;s
common for the process to retry connect(), and if the connection is
successful the socket will be added to the connected table a second
time, corrupting the list.&lt;/p&gt;
&lt;p&gt;Prevent this by calling vsock_remove_connected() if a signal is received
while waiting for a connection. This is harmless if the socket is not in
the connected table, and if it is in the table then removing it will
prevent list corruption from a double add.&lt;/p&gt;
&lt;p&gt;Note for backporting: this patch requires d5afa82c977e (&amp;#34;vsock: correct
removal of socket from the list&amp;#34;), which is in all current stable trees
except 4.9.y.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-48786</guid>
    </item>
  </channel>
</rss>
