<?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-09-29T20:16:07.250870+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-38717</id>
    <title>CVE-2025-38717 — net: kcm: Fix race condition in kcm_unattach()</title>
    <updated>2026-09-29T20:16:07.252618+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>net: kcm: Fix race condition in kcm_unattach()</p>
<p>syzbot found a race condition when kcm_unattach(psock)
and kcm_release(kcm) are executed at the same time.</p>
<p>kcm_unattach() is missing a check of the flag
kcm-&gt;tx_stopped before calling queue_work().</p>
<p>If the kcm has a reserved psock, kcm_unattach() might get executed
between cancel_work_sync() and unreserve_psock() in kcm_release(),
requeuing kcm-&gt;tx_work right before kcm gets freed in kcm_done().</p>
<p>Remove kcm-&gt;tx_stopped and replace it by the less
error-prone disable_work_sync().</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-38717"/>
  </entry>
</feed>
