Local kernel crash via preemptible CPU lookup
Published Oct 4, 2025 · Updated Oct 4, 2025
Denial of service in the Linux kernel intel_powerclamp driver allows local users to crash the kernel during idle injection. powerclamp_set_cur_state() uses smp_processor_id() in preemptible code after selecting a replacement control CPU when CPU 0 is offline, triggering the kernel BUG check. Reachability requires CPU 0 to be offline and intel_powerclamp to inject idle; the reported consequence is a kernel crash, not data disclosure or modification.
Summary
What happened
Denial of service in the Linux kernel intel_powerclamp driver allows local users to crash the kernel during idle injection. powerclamp_set_cur_state() uses smp_processor_id() in preemptible code after selecting a replacement control CPU when CPU 0 is offline, triggering the kernel BUG check. Reachability requires CPU 0 to be offline and intel_powerclamp to inject idle; the reported consequence is a kernel crash, not data disclosure or modification.
The record
- CVE
- CVE-2022-50494
- Published
- Oct 4, 2025
- Updated
- Oct 4, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 4, 2025CVE publishedPublication date reported by the CVE source.
- Oct 4, 2025Record 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0f91f66c568b316b19cb042cf50584467b3bdff4
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3e799e815097febbcb81b472285be824f5d089f9
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <418fae0700e85a498062424f8656435c32cdb200
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <513943bf879d45005213e6f5cfb7d9e9943f589f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5614908434451aafbf9b24cb5247cf1d21269f76
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5a646c38f648185ee2c62f2a19da3c6f04e27612
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <68b99e94a4a2db6ba9b31fe0485e057b9354a640
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6904727db0eb62fb0c2dce1cf331c341d97ee4b7
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6e2a347b304224b2aeb1c0ea000d1cf8a02cc592
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