[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091147-CVE-2025-39774-9da3@gregkh>
Date: Thu, 11 Sep 2025 18:56:53 +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-39774: iio: adc: rzg2l_adc: Set driver data before enabling runtime PM
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
iio: adc: rzg2l_adc: Set driver data before enabling runtime PM
When stress-testing the system by repeatedly unbinding and binding the ADC
device in a loop, and the ADC is a supplier for another device (e.g., a
thermal hardware block that reads temperature through the ADC), it may
happen that the ADC device is runtime-resumed immediately after runtime PM
is enabled, triggered by its consumer. At this point, since drvdata is not
yet set and the driver's runtime PM callbacks rely on it, a crash can
occur. To avoid this, set drvdata just after it was allocated.
The Linux kernel CVE team has assigned CVE-2025-39774 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.14 with commit 89ee8174e8c8db0efc75b26f2307114b38d61354 and fixed in 6.16.4 with commit e7ce902db071a7b3e696a43d6e14ca57360deee6
Issue introduced in 6.14 with commit 89ee8174e8c8db0efc75b26f2307114b38d61354 and fixed in 6.17-rc3 with commit c69e13965f26b8058f538ea8bdbd2d7718cf1fbe
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-39774
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/iio/adc/rzg2l_adc.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/e7ce902db071a7b3e696a43d6e14ca57360deee6
https://git.kernel.org/stable/c/c69e13965f26b8058f538ea8bdbd2d7718cf1fbe
Powered by blists - more mailing lists