<?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 10:07:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21666 — vsock: prevent null-ptr-deref in vsock_*[has_data|has_space]</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-21666</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vsock: prevent null-ptr-deref in vsock_*[has_data|has_space]&lt;/p&gt;
&lt;p&gt;Recent reports have shown how we sometimes call vsock_*_has_data()
when a vsock socket has been de-assigned from a transport (see attached
links), but we shouldn&amp;#39;t.&lt;/p&gt;
&lt;p&gt;Previous commits should have solved the real problems, but we may have
more in the future, so to avoid null-ptr-deref, we can return 0
(no space, no data available) but with a warning.&lt;/p&gt;
&lt;p&gt;This way the code should continue to run in a nearly consistent state
and have a warning that allows us to debug future problems.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vsock: prevent null-ptr-deref in vsock_*[has_data|has_space]&lt;/p&gt;
&lt;p&gt;Recent reports have shown how we sometimes call vsock_*_has_data()
when a vsock socket has been de-assigned from a transport (see attached
links), but we shouldn&amp;#39;t.&lt;/p&gt;
&lt;p&gt;Previous commits should have solved the real problems, but we may have
more in the future, so to avoid null-ptr-deref, we can return 0
(no space, no data available) but with a warning.&lt;/p&gt;
&lt;p&gt;This way the code should continue to run in a nearly consistent state
and have a warning that allows us to debug future problems.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-21666</guid>
    </item>
  </channel>
</rss>
