<?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>Mon, 05 Oct 2026 02:11:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-37802 — ksmbd: fix WARNING "do not call blocking ops when !TASK_RUNNING"</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-37802</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix WARNING &amp;#34;do not call blocking ops when !TASK_RUNNING&amp;#34;&lt;/p&gt;
&lt;p&gt;wait_event_timeout() will set the state of the current
task to TASK_UNINTERRUPTIBLE, before doing the condition check. This
means that ksmbd_durable_scavenger_alive() will try to acquire the mutex
while already in a sleeping state. The scheduler warns us by giving
the following warning:&lt;/p&gt;
&lt;p&gt;do not call blocking ops when !TASK_RUNNING; state=2 set at
 [&amp;lt;0000000061515a6f&amp;gt;] prepare_to_wait_event+0x9f/0x6c0
WARNING: CPU: 2 PID: 4147 at kernel/sched/core.c:10099 __might_sleep+0x12f/0x160&lt;/p&gt;
&lt;p&gt;mutex lock is not needed in ksmbd_durable_scavenger_alive().&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix WARNING &amp;#34;do not call blocking ops when !TASK_RUNNING&amp;#34;&lt;/p&gt;
&lt;p&gt;wait_event_timeout() will set the state of the current
task to TASK_UNINTERRUPTIBLE, before doing the condition check. This
means that ksmbd_durable_scavenger_alive() will try to acquire the mutex
while already in a sleeping state. The scheduler warns us by giving
the following warning:&lt;/p&gt;
&lt;p&gt;do not call blocking ops when !TASK_RUNNING; state=2 set at
 [&amp;lt;0000000061515a6f&amp;gt;] prepare_to_wait_event+0x9f/0x6c0
WARNING: CPU: 2 PID: 4147 at kernel/sched/core.c:10099 __might_sleep+0x12f/0x160&lt;/p&gt;
&lt;p&gt;mutex lock is not needed in ksmbd_durable_scavenger_alive().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-37802</guid>
    </item>
  </channel>
</rss>
