linux-cve-announce - CVE-2025-39712: media: mt9m114: Fix deadlock in get_frame_interval/set_frame

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025090550-CVE-2025-39712-6910@gregkh>
Date: Fri,  5 Sep 2025 19:21: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-39712: media: mt9m114: Fix deadlock in get_frame_interval/set_frame_interval

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

media: mt9m114: Fix deadlock in get_frame_interval/set_frame_interval

Getting / Setting the frame interval using the V4L2 subdev pad ops
get_frame_interval/set_frame_interval causes a deadlock, as the
subdev state is locked in the [1] but also in the driver itself.

In [2] it's described that the caller is responsible to acquire and
release the lock in this case. Therefore, acquiring the lock in the
driver is wrong.

Remove the lock acquisitions/releases from mt9m114_ifp_get_frame_interval()
and mt9m114_ifp_set_frame_interval().

[1] drivers/media/v4l2-core/v4l2-subdev.c - line 1129
[2] Documentation/driver-api/media/v4l2-subdev.rst

The Linux kernel CVE team has assigned CVE-2025-39712 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.7 with commit 24d756e914fc3418bad7897b0657aefa9ef848e8 and fixed in 6.12.44 with commit 0d23b548d71e5d76955fdf1d73addd8f6494f602
	Issue introduced in 6.7 with commit 24d756e914fc3418bad7897b0657aefa9ef848e8 and fixed in 6.16.4 with commit 41b97490a1656bdc7038d6345a84b08d45deafc6
	Issue introduced in 6.7 with commit 24d756e914fc3418bad7897b0657aefa9ef848e8 and fixed in 6.17-rc1 with commit 298d1471cf83d5a2a05970e41822a2403f451086

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-39712
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/media/i2c/mt9m114.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/0d23b548d71e5d76955fdf1d73addd8f6494f602
	https://git.kernel.org/stable/c/41b97490a1656bdc7038d6345a84b08d45deafc6
	https://git.kernel.org/stable/c/298d1471cf83d5a2a05970e41822a2403f451086