[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025050918-CVE-2025-37847-c856@gregkh>
Date: Fri, 9 May 2025 08:42:25 +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-37847: accel/ivpu: Fix deadlock in ivpu_ms_cleanup()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
accel/ivpu: Fix deadlock in ivpu_ms_cleanup()
Fix deadlock in ivpu_ms_cleanup() by preventing runtime resume after
file_priv->ms_lock is acquired.
During a failure in runtime resume, a cold boot is executed, which
calls ivpu_ms_cleanup_all(). This function calls ivpu_ms_cleanup()
that acquires file_priv->ms_lock and causes the deadlock.
The Linux kernel CVE team has assigned CVE-2025-37847 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.11 with commit cdfad4db7756563db7d458216d9e3c2651dddc7d and fixed in 6.12.24 with commit 7d12a7d43c7bab9097ba466581d8db702e7908dc
Issue introduced in 6.11 with commit cdfad4db7756563db7d458216d9e3c2651dddc7d and fixed in 6.13.12 with commit f996ecc789b5dbaaf38b6ec0a1917821789cbd9c
Issue introduced in 6.11 with commit cdfad4db7756563db7d458216d9e3c2651dddc7d and fixed in 6.14.3 with commit 019634f27a16796eab749e8107dae32099945f29
Issue introduced in 6.11 with commit cdfad4db7756563db7d458216d9e3c2651dddc7d and fixed in 6.15-rc2 with commit 9a6f56762d23a1f3af15e67901493c927caaf882
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-37847
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/accel/ivpu/ivpu_ms.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/7d12a7d43c7bab9097ba466581d8db702e7908dc
https://git.kernel.org/stable/c/f996ecc789b5dbaaf38b6ec0a1917821789cbd9c
https://git.kernel.org/stable/c/019634f27a16796eab749e8107dae32099945f29
https://git.kernel.org/stable/c/9a6f56762d23a1f3af15e67901493c927caaf882
Powered by blists - more mailing lists