CVE-2024-49985

Medium

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.

SeverityMedium
CVSS5.5
Exploit probability—
ProductLinux Kernel
PublishedOct 21, 2024
First seenOct 21, 2024

How to fix

Update
  • linux linux_kernel5.10.227, 5.15.168, 6.1.113, 6.6.55, 6.10.14, 6.11.3 or later

Affected products

ProductAffected versionsFixed in
linux linux_kernel5.0 ≤ v < 5.10.227, 5.11 ≤ v < 5.15.168, 5.16 ≤ v < 6.1.113, 6.2 ≤ v < 6.6.55, 6.7 ≤ v < 6.10.14, 6.11 ≤ v < 6.11.3, 6.125.10.227, 5.15.168, 6.1.113, 6.6.55, 6.10.14, 6.11.3

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.

CVE-2024-49985 · Linux Kernel · Dark Radar