<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T01:18:39.636107+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2025-21666</id>
    <title>CVE-2025-21666 — vsock: prevent null-ptr-deref in vsock_*[has_data|has_space]</title>
    <updated>2026-10-02T01:18:39.639184+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux, Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>vsock: prevent null-ptr-deref in vsock_*[has_data|has_space]</p>
<p>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't.</p>
<p>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.</p>
<p>This way the code should continue to run in a nearly consistent state
and have a warning that allows us to debug future problems.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-21666"/>
  </entry>
</feed>
