[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025052057-CVE-2025-37906-0bd6@gregkh>
Date: Tue, 20 May 2025 17:22:03 +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-37906: ublk: fix race between io_uring_cmd_complete_in_task and ublk_cancel_cmd
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ublk: fix race between io_uring_cmd_complete_in_task and ublk_cancel_cmd
ublk_cancel_cmd() calls io_uring_cmd_done() to complete uring_cmd, but
we may have scheduled task work via io_uring_cmd_complete_in_task() for
dispatching request, then kernel crash can be triggered.
Fix it by not trying to canceling the command if ublk block request is
started.
The Linux kernel CVE team has assigned CVE-2025-37906 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.7 with commit 216c8f5ef0f209a3797292c487bdaa6991ab4b92 and fixed in 6.14.6 with commit fb2eb9ddf556f93fef45201e1f9d2b8674bcc975
Issue introduced in 6.7 with commit 216c8f5ef0f209a3797292c487bdaa6991ab4b92 and fixed in 6.15-rc4 with commit f40139fde5278d81af3227444fd6e76a76b9506d
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-37906
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:
drivers/block/ublk_drv.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/fb2eb9ddf556f93fef45201e1f9d2b8674bcc975
https://git.kernel.org/stable/c/f40139fde5278d81af3227444fd6e76a76b9506d
Powered by blists - more mailing lists