Service interruption via atomic-context power management
Published Aug 17, 2024 · Updated May 11, 2026
Incorrect runtime power management in the Linux kernel allows local users to interrupt service during device probing. The imx-irqsteer resume path calls clk_prepare while atomic, while platform power-on handling can sleep, producing a scheduling-while-atomic fault. Reachability requires an i.MX8QM or i.MX8QXP-class platform using this controller and a probe path that resumes its power domain; the bounded impact is loss of availability.
Summary
What happened
Incorrect runtime power management in the Linux kernel allows local users to interrupt service during device probing. The imx-irqsteer resume path calls clk_prepare while atomic, while platform power-on handling can sleep, producing a scheduling-while-atomic fault. Reachability requires an i.MX8QM or i.MX8QXP-class platform using this controller and a probe path that resumes its power domain; the bounded impact is loss of availability.
The record
- CVE
- CVE-2024-42290
- Published
- Aug 17, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 17, 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=0136afa08967f6e160b9b4e85a7a70e4180a8333 <21bd3f9e7f924cd2fc892a484e7a50c7e1847565
- Affected versionversion=0136afa08967f6e160b9b4e85a7a70e4180a8333 <33b1c47d1fc0b5f06a393bb915db85baacba18ea
- Affected versionversion=0136afa08967f6e160b9b4e85a7a70e4180a8333 <3a2884a44e5cda192df1b28e9925661f79f599a1
- Affected versionversion=0136afa08967f6e160b9b4e85a7a70e4180a8333 <58c56735facb225a5c46fa4b8bbbe7f31d1cb894
- Affected versionversion=0136afa08967f6e160b9b4e85a7a70e4180a8333 <a590e8dea3df2639921f874d763be961dd74e8f9
- Affected versionversion=0136afa08967f6e160b9b4e85a7a70e4180a8333 <f8ae38f1dfe652779c7c613facbc257cec00ac44
- Affected versionversion=0136afa08967f6e160b9b4e85a7a70e4180a8333 <fa1803401e1c360efe6342fb41d161cc51748a11
- 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.
Weakness, pattern, technique
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