<?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-28T20:56:21.514714+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-39736</id>
    <title>CVE-2025-39736 — mm/kmemleak: avoid deadlock by moving pr_warn() outside kmemleak_lock</title>
    <updated>2026-09-28T20:56:21.518264+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux, Siemens SIMATIC CN 4100</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>mm/kmemleak: avoid deadlock by moving pr_warn() outside kmemleak_lock</p>
<p>When netpoll is enabled, calling pr_warn_once() while holding
kmemleak_lock in mem_pool_alloc() can cause a deadlock due to lock
inversion with the netconsole subsystem.  This occurs because
pr_warn_once() may trigger netpoll, which eventually leads to
__alloc_skb() and back into kmemleak code, attempting to reacquire
kmemleak_lock.</p>
<p>This is the path for the deadlock.</p>
<p>mem_pool_alloc()
  -&gt; raw_spin_lock_irqsave(&amp;kmemleak_lock, flags);
      -&gt; pr_warn_once()
          -&gt; netconsole subsystem
	     -&gt; netpoll
	         -&gt; __alloc_skb
		   -&gt; __create_object
		     -&gt; raw_spin_lock_irqsave(&amp;kmemleak_lock, flags);</p>
<p>Fix this by setting a flag and issuing the pr_warn_once() after
kmemleak_lock is released.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-39736"/>
  </entry>
</feed>
