CVE-2024-49985
STM32F7 I2C Clock Deadlock Vulnerability
Description
In the Linux kernel, the following vulnerability has been resolved: i2c: stm32f7: Do not prepare/unprepare clock during runtime suspend/resume In case there is any sort of clock controller attached to this I2C bus controller, for example Versaclock or even an AIC32x4 I2C codec, then an I2C transfer triggered from the clock controller clk_ops .prepare callback may trigger a deadlock on drivers/clk/clk.c prepare_lock mutex. This is because the clock controller first grabs the prepare_lock mutex and then performs the prepare operation, including its I2C access. The I2C access resumes this I2C bus controller via .runtime_resume callback, which calls clk_prepare_enable(), which attempts to grab the prepare_lock mutex again and deadlocks. Since the clock are already prepared since probe() and unprepared in remove(), use simple clk_enable()/clk_disable() calls to enable and disable the clock on runtime suspend and resume, to avoid hitting the prepare_lock mutex.
INFO
Published Date :
Oct. 21, 2024, 6:15 p.m.
Last Modified :
Nov. 8, 2024, 4:15 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
3.6
Exploitability Score :
1.8
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-49985.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-49985 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-49985 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Nov. 08, 2024
Action Type Old Value New Value Added Reference kernel.org https://git.kernel.org/stable/c/d6f1250a4d5773f447740b9fe37b8692105796d4 [No types assigned] -
Initial Analysis by [email protected]
Oct. 28, 2024
Action Type Old Value New Value Added CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Changed Reference Type https://git.kernel.org/stable/c/048bbbdbf85e5e00258dfb12f5e368f908801d7b No Types Assigned https://git.kernel.org/stable/c/048bbbdbf85e5e00258dfb12f5e368f908801d7b Patch Changed Reference Type https://git.kernel.org/stable/c/1883cad2cc629ded4a3556c0bbb8b42533ad8764 No Types Assigned https://git.kernel.org/stable/c/1883cad2cc629ded4a3556c0bbb8b42533ad8764 Patch Changed Reference Type https://git.kernel.org/stable/c/22a1f8a5b56ba93d3e8b7a1dafa24e01c8bb48ba No Types Assigned https://git.kernel.org/stable/c/22a1f8a5b56ba93d3e8b7a1dafa24e01c8bb48ba Patch Changed Reference Type https://git.kernel.org/stable/c/894cd5f5fd9061983445bbd1fa3d81be43095344 No Types Assigned https://git.kernel.org/stable/c/894cd5f5fd9061983445bbd1fa3d81be43095344 Patch Changed Reference Type https://git.kernel.org/stable/c/9b8bc33ad64192f54142396470cc34ce539a8940 No Types Assigned https://git.kernel.org/stable/c/9b8bc33ad64192f54142396470cc34ce539a8940 Patch Changed Reference Type https://git.kernel.org/stable/c/c2024b1a583ab9176c797ea1e5f57baf8d5e2682 No Types Assigned https://git.kernel.org/stable/c/c2024b1a583ab9176c797ea1e5f57baf8d5e2682 Patch Changed Reference Type https://git.kernel.org/stable/c/fac3c9f7784e8184c0338e9f0877b81e55d3ef1c No Types Assigned https://git.kernel.org/stable/c/fac3c9f7784e8184c0338e9f0877b81e55d3ef1c Patch Added CWE NIST CWE-667 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.0 up to (excluding) 5.10.227 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.168 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.113 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.55 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.10.14 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.11 up to (excluding) 6.11.3 *cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:* -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Oct. 21, 2024
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: i2c: stm32f7: Do not prepare/unprepare clock during runtime suspend/resume In case there is any sort of clock controller attached to this I2C bus controller, for example Versaclock or even an AIC32x4 I2C codec, then an I2C transfer triggered from the clock controller clk_ops .prepare callback may trigger a deadlock on drivers/clk/clk.c prepare_lock mutex. This is because the clock controller first grabs the prepare_lock mutex and then performs the prepare operation, including its I2C access. The I2C access resumes this I2C bus controller via .runtime_resume callback, which calls clk_prepare_enable(), which attempts to grab the prepare_lock mutex again and deadlocks. Since the clock are already prepared since probe() and unprepared in remove(), use simple clk_enable()/clk_disable() calls to enable and disable the clock on runtime suspend and resume, to avoid hitting the prepare_lock mutex. Added Reference kernel.org https://git.kernel.org/stable/c/9b8bc33ad64192f54142396470cc34ce539a8940 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/1883cad2cc629ded4a3556c0bbb8b42533ad8764 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/c2024b1a583ab9176c797ea1e5f57baf8d5e2682 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/22a1f8a5b56ba93d3e8b7a1dafa24e01c8bb48ba [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/fac3c9f7784e8184c0338e9f0877b81e55d3ef1c [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/894cd5f5fd9061983445bbd1fa3d81be43095344 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/048bbbdbf85e5e00258dfb12f5e368f908801d7b [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-49985 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-49985
weaknesses.