Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-49985i2c: stm32f7: Do not prepare/unprepare clock during runtime suspend/resume

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 19 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-49985, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 4e7bca6fc07bf9526d797b9787dcb21e40cd10cf – < d6f1250a4d5773f447740b9fe37b8692105796d4
    • affected 4e7bca6fc07bf9526d797b9787dcb21e40cd10cf – < 9b8bc33ad64192f54142396470cc34ce539a8940
    • affected 4e7bca6fc07bf9526d797b9787dcb21e40cd10cf – < 1883cad2cc629ded4a3556c0bbb8b42533ad8764
    • affected 4e7bca6fc07bf9526d797b9787dcb21e40cd10cf – < c2024b1a583ab9176c797ea1e5f57baf8d5e2682
    • affected 4e7bca6fc07bf9526d797b9787dcb21e40cd10cf – < 22a1f8a5b56ba93d3e8b7a1dafa24e01c8bb48ba
    • affected 4e7bca6fc07bf9526d797b9787dcb21e40cd10cf – < fac3c9f7784e8184c0338e9f0877b81e55d3ef1c
    • affected 4e7bca6fc07bf9526d797b9787dcb21e40cd10cf – < 894cd5f5fd9061983445bbd1fa3d81be43095344
    • affected 4e7bca6fc07bf9526d797b9787dcb21e40cd10cf – < 048bbbdbf85e5e00258dfb12f5e368f908801d7b
  • Linux · Linux

    • affected 5.0
    • unaffected < 5.0
    • unaffected 5.4.285 – ≤ 5.4.*
    • unaffected 5.10.227 – ≤ 5.10.*
    • unaffected 5.15.168 – ≤ 5.15.*
    • unaffected 6.1.113 – ≤ 6.1.*
    • unaffected 6.6.55 – ≤ 6.6.*
    • unaffected 6.10.14 – ≤ 6.10.*
    • unaffected 6.11.3 – ≤ 6.11.*
    • unaffected 6.12 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-49985 badge
[![CVE-2024-49985](https://cveledger.app/badge/CVE-2024-49985.svg)](https://cveledger.app/cve/CVE-2024-49985)

Record last updated .