<?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-30T16:38:31.941973+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-2022-49957</id>
    <title>CVE-2022-49957 — kcm: fix strp_init() order and cleanup</title>
    <updated>2026-09-30T16:38:31.944707+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>kcm: fix strp_init() order and cleanup</p>
<p>strp_init() is called just a few lines above this csk-&gt;sk_user_data
check, it also initializes strp-&gt;work etc., therefore, it is
unnecessary to call strp_done() to cancel the freshly initialized
work.</p>
<p>And if sk_user_data is already used by KCM, psock-&gt;strp should not be
touched, particularly strp-&gt;work state, so we need to move strp_init()
after the csk-&gt;sk_user_data check.</p>
<p>This also makes a lockdep warning reported by syzbot go away.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2022-49957"/>
  </entry>
</feed>
