[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025050814-CVE-2025-37802-0f78@gregkh>
Date: Thu, 8 May 2025 08:39:11 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-37802: ksmbd: fix WARNING "do not call blocking ops when !TASK_RUNNING"
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix WARNING "do not call blocking ops when !TASK_RUNNING"
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:
do not call blocking ops when !TASK_RUNNING; state=2 set at
[<0000000061515a6f>] prepare_to_wait_event+0x9f/0x6c0
WARNING: CPU: 2 PID: 4147 at kernel/sched/core.c:10099 __might_sleep+0x12f/0x160
mutex lock is not needed in ksmbd_durable_scavenger_alive().
The Linux kernel CVE team has assigned CVE-2025-37802 to this issue.
Affected and fixed versions
===========================
Fixed in 6.12.26 with commit 8f805b3746d2f41702c77cba22f94f8415fadd1a
Fixed in 6.14.5 with commit cd161198e091e8a62b9bd631be970ea9a87d2d6a
Fixed in 6.15-rc3 with commit 1df0d4c616138784e033ad337961b6e1a6bcd999
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2025-37802
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
fs/smb/server/vfs_cache.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/8f805b3746d2f41702c77cba22f94f8415fadd1a
https://git.kernel.org/stable/c/cd161198e091e8a62b9bd631be970ea9a87d2d6a
https://git.kernel.org/stable/c/1df0d4c616138784e033ad337961b6e1a6bcd999
Powered by blists - more mailing lists