Kernel crash via uninitialized cpufreq completion
Published Oct 4, 2025 · Updated Oct 4, 2025
Use of an uninitialized resource in Linux kernel cpufreq allows local users to crash the kernel during CPU-frequency driver setup. cpufreq_policy_alloc initializes its completion after kobject_init_and_add, so the failure path reaches cpufreq_sysfs_release and completes an uninitialized object. Exploitation requires local low-privileged access and failed kobject registration; the consequence is limited to a kernel crash.
Summary
What happened
Use of an uninitialized resource in Linux kernel cpufreq allows local users to crash the kernel during CPU-frequency driver setup. cpufreq_policy_alloc initializes its completion after kobject_init_and_add, so the failure path reaches cpufreq_sysfs_release and completes an uninitialized object. Exploitation requires local low-privileged access and failed kobject registration; the consequence is limited to a kernel crash.
The record
- CVE
- CVE-2022-50473
- Published
- Oct 4, 2025
- Updated
- Oct 4, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-908, 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=4ebe36c94aed95de71a8ce6a6762226d31c938ee <3cdd91a9163248935720927531066b74f57aa43b
- Affected versionversion=4ebe36c94aed95de71a8ce6a6762226d31c938ee <5c51054896bcce1d33d39fead2af73fec24f40b6
- Affected versionversion=4ebe36c94aed95de71a8ce6a6762226d31c938ee <8fb4c98f20dfca1237de2e3dfdbe78d156784fd3
- Affected versionversion=4ebe36c94aed95de71a8ce6a6762226d31c938ee <d88540acfc7a17079021d866de914112c396edb1
- Affected versionversion=4ebe36c94aed95de71a8ce6a6762226d31c938ee <e379b88a8f8cffc99b318e028705ed9e3da0e1e0
- Affected versionversion=4ebe36c94aed95de71a8ce6a6762226d31c938ee <e7c0c943ed675b66d4bbb16c51c6a3bb58da047e
- Affected versionversion=5.2
- Affected versionversion=e977b1477a6725868302957e6b5c330220391797
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