[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025072559-CVE-2025-38369-6ddf@gregkh>
Date: Fri, 25 Jul 2025 14:48:10 +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-38369: dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: idxd: Check availability of workqueue allocated by idxd wq driver before using
Running IDXD workloads in a container with the /dev directory mounted can
trigger a call trace or even a kernel panic when the parent process of the
container is terminated.
This issue occurs because, under certain configurations, Docker does not
properly propagate the mount replica back to the original mount point.
In this case, when the user driver detaches, the WQ is destroyed but it
still calls destroy_workqueue() attempting to completes all pending work.
It's necessary to check wq->wq and skip the drain if it no longer exists.
The Linux kernel CVE team has assigned CVE-2025-38369 to this issue.
Affected and fixed versions
===========================
Fixed in 6.6.96 with commit e0051a3daa8b2cb318b03b2f9317c3e40855847a
Fixed in 6.12.36 with commit 98fd66c8ba77e3a7137575f610271014bc0e701f
Fixed in 6.15.5 with commit aee7a7439f8c0884da87694a401930204a57128f
Fixed in 6.16-rc1 with commit 17502e7d7b7113346296f6758324798d536c31fd
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-38369
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/dma/idxd/cdev.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/e0051a3daa8b2cb318b03b2f9317c3e40855847a
https://git.kernel.org/stable/c/98fd66c8ba77e3a7137575f610271014bc0e701f
https://git.kernel.org/stable/c/aee7a7439f8c0884da87694a401930204a57128f
https://git.kernel.org/stable/c/17502e7d7b7113346296f6758324798d536c31fd
Powered by blists - more mailing lists