System hang via recursive clock preparation deadlock
Published Oct 21, 2024 · Updated May 11, 2026
Denial of service in the Linux kernel allows local users to hang systems by triggering an STM32F7 I2C controller runtime resume. An attached clock controller holds prepare_lock while its prepare callback initiates I2C access; runtime resume then calls clk_prepare_enable and recursively requests the same mutex. The path requires that hardware topology, and the resulting deadlock blocks progress rather than disclosing or altering data.
Summary
What happened
Denial of service in the Linux kernel allows local users to hang systems by triggering an STM32F7 I2C controller runtime resume. An attached clock controller holds prepare_lock while its prepare callback initiates I2C access; runtime resume then calls clk_prepare_enable and recursively requests the same mutex. The path requires that hardware topology, and the resulting deadlock blocks progress rather than disclosing or altering data.
The record
- CVE
- CVE-2024-49985
- Published
- Oct 21, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4e7bca6fc07bf9526d797b9787dcb21e40cd10cf <048bbbdbf85e5e00258dfb12f5e368f908801d7b
- Affected versionversion=4e7bca6fc07bf9526d797b9787dcb21e40cd10cf <1883cad2cc629ded4a3556c0bbb8b42533ad8764
- Affected versionversion=4e7bca6fc07bf9526d797b9787dcb21e40cd10cf <22a1f8a5b56ba93d3e8b7a1dafa24e01c8bb48ba
- Affected versionversion=4e7bca6fc07bf9526d797b9787dcb21e40cd10cf <894cd5f5fd9061983445bbd1fa3d81be43095344
- Affected versionversion=4e7bca6fc07bf9526d797b9787dcb21e40cd10cf <9b8bc33ad64192f54142396470cc34ce539a8940
- Affected versionversion=4e7bca6fc07bf9526d797b9787dcb21e40cd10cf <c2024b1a583ab9176c797ea1e5f57baf8d5e2682
- Affected versionversion=4e7bca6fc07bf9526d797b9787dcb21e40cd10cf <d6f1250a4d5773f447740b9fe37b8692105796d4
- Affected versionversion=4e7bca6fc07bf9526d797b9787dcb21e40cd10cf <fac3c9f7784e8184c0338e9f0877b81e55d3ef1c
- Affected versionversion=5.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo