Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 048bbbdbf85e5e00258dfb12f5e368f908801d7b, 1883cad2cc629ded4a3556c0bbb8b42533ad8764, 22a1f8a5b56ba93d3e8b7a1dafa24e01c8bb48ba; azl3 kernel 6.6.51.1-5 on Azure Linux 3.0 6.6.57.1-2; azl3 kernel 6.6.57.1-2 on Azure Linux 3.0 6.6.57.1-2.

Low priority for now. Upgrade to Linux Linux 048bbbdbf85e5e00258dfb12f5e368f908801d7b, 1883cad2cc629ded4a3556c0bbb8b42533ad8764, 22a1f8a5b56ba93d3e8b7a1dafa24e01c8bb48ba; azl3 kernel 6.6.51.1-5 on Azure Linux 3.0 6.6.57.1-2; azl3 kernel 6.6.57.1-2 on Azure Linux 3.0 6.6.57.1-2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Oct 21, 2024
Updated
Jun 17, 2026
EPSS
0.1% · 9th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-49985

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.0 and later · before 5.10.227
  • linux linux kernel5.11 and later · before 5.15.168
  • linux linux kernel5.16 and later · before 6.1.113
  • linux linux kernel6.2 and later · before 6.6.55
  • linux linux kernel6.7 and later · before 6.10.14
  • linux linux kernel6.11 and later · before 6.11.3
  • linux linux kernel6.12

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.0affected
    • 4e7bca6fc07bf9526d797b9787dcb21e40cd10cf and later · before d6f1250a4d5773f447740b9fe37b8692105796d4affected · git
    • 4e7bca6fc07bf9526d797b9787dcb21e40cd10cf and later · before 9b8bc33ad64192f54142396470cc34ce539a8940affected · git
    • 4e7bca6fc07bf9526d797b9787dcb21e40cd10cf and later · before 1883cad2cc629ded4a3556c0bbb8b42533ad8764affected · git
    • 4e7bca6fc07bf9526d797b9787dcb21e40cd10cf and later · before c2024b1a583ab9176c797ea1e5f57baf8d5e2682affected · git
    • 4e7bca6fc07bf9526d797b9787dcb21e40cd10cf and later · before 22a1f8a5b56ba93d3e8b7a1dafa24e01c8bb48baaffected · git
    • 4e7bca6fc07bf9526d797b9787dcb21e40cd10cf and later · before fac3c9f7784e8184c0338e9f0877b81e55d3ef1caffected · git
    • 4e7bca6fc07bf9526d797b9787dcb21e40cd10cf and later · before 894cd5f5fd9061983445bbd1fa3d81be43095344affected · git
    • 4e7bca6fc07bf9526d797b9787dcb21e40cd10cf and later · before 048bbbdbf85e5e00258dfb12f5e368f908801d7baffected · git
    • before 5.0not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.115-16.1.115-1
Debian:13linuxbefore 6.11.4-16.11.4-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-49983Oct 21, 2024 · ext4: drop ppath from ext4_ext_replay_update_ex() to avoid double-free
    31Monitor
  • ← EarlierCVE-2024-49984Oct 21, 2024 · drm/v3d: Prevent out of bounds access in performance query extensions
    31Monitor
  • Later →CVE-2024-49986Oct 21, 2024 · platform/x86: x86-android-tablets: Fix use after free on platform_device_register() errors
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux048bbbdbf85e5e00258dfb12f5e368f908801d7bVendor (CNA)
Linux Linux1883cad2cc629ded4a3556c0bbb8b42533ad8764Vendor (CNA)
Linux Linux22a1f8a5b56ba93d3e8b7a1dafa24e01c8bb48baVendor (CNA)
Linux Linux894cd5f5fd9061983445bbd1fa3d81be43095344Vendor (CNA)
Linux Linux9b8bc33ad64192f54142396470cc34ce539a8940Vendor (CNA)
Linux Linuxc2024b1a583ab9176c797ea1e5f57baf8d5e2682Vendor (CNA)
Linux Linuxd6f1250a4d5773f447740b9fe37b8692105796d4Vendor (CNA)
Linux Linuxfac3c9f7784e8184c0338e9f0877b81e55d3ef1cVendor (CNA)
azl3 kernel 6.6.51.1-5 on Azure Linux 3.06.6.57.1-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.57.1-2 on Azure Linux 3.06.6.57.1-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.167.1-2 on CBL Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.167.1-2 on CBL-Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.173.1-1 on CBL Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.115-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-667 · Improper Locking

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (9 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records