Local availability disruption via IRQ-state corruption
Published Feb 26, 2025 · Updated May 11, 2026
IRQ-state corruption in Linux kernel power management allows local users to disrupt availability during power-domain attachment. device_pm_check_callbacks() uses spin_lock_irq() and spin_unlock_irq() while it can run beneath a spinlock, so the pair fails to preserve the caller's interrupt flags. The affected path requires a generic power domain configured with spinlocks; the documented result is invalid interrupt restoration and a kernel warning.
Summary
What happened
IRQ-state corruption in Linux kernel power management allows local users to disrupt availability during power-domain attachment. device_pm_check_callbacks() uses spin_lock_irq() and spin_unlock_irq() while it can run beneath a spinlock, so the pair fails to preserve the caller's interrupt flags. The affected path requires a generic power domain configured with spinlocks; the documented result is invalid interrupt restoration and a kernel warning.
The record
- CVE
- CVE-2022-49175
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2025CVE 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=4.5
- Affected versionversion=aa8e54b559479d0cb7eb632ba443b8cacd20cd4b <0cccf9d4fb45f1acbc0bbf6d7e4d8d0fb7a10416
- Affected versionversion=aa8e54b559479d0cb7eb632ba443b8cacd20cd4b <2add538e57a2825c61d639260386f385c75e4166
- Affected versionversion=aa8e54b559479d0cb7eb632ba443b8cacd20cd4b <3ec80d52b9b74b9e691997632a543c73eddfeba0
- Affected versionversion=aa8e54b559479d0cb7eb632ba443b8cacd20cd4b <524bb1da785a7ae43dd413cd392b5071c6c367f8
- Affected versionversion=aa8e54b559479d0cb7eb632ba443b8cacd20cd4b <78c4d68b952f5f537788dbd454031ea9bf50f642
- Affected versionversion=aa8e54b559479d0cb7eb632ba443b8cacd20cd4b <be8bc05f38d667eda1e820bc6f69234795be7809
- Affected versionversion=aa8e54b559479d0cb7eb632ba443b8cacd20cd4b <c29642ba72f87c0a3d7449f7db5d6d76a7ed53c3
- Affected versionversion=aa8e54b559479d0cb7eb632ba443b8cacd20cd4b <c7c0ec5a1dcc3eaa1e85c804c2ccf46e457788a3
- Affected versionversion=aa8e54b559479d0cb7eb632ba443b8cacd20cd4b <ede1ef1a7de973321699736ef96d01a4b9a6fe9e
What conditions does exploitation require?
What is affected?
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
No sourced classifications are available.
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