CVE-2022-50012
Last modified
CVE-2022-50012 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: powerpc/64: Init jump labels before parse_early_param() On 64-bit, calling jump_label_init() in setup_feature_keys() is too late because static keys may be used in subroutines of parse_early_param() which is again subroutine of early_init_devtree(). For example booting with "threadirqs": static_key_enable_cpuslocked(): static key '0xc000000002953260' used before call to jump_label_init() WARNING: CPU: 0 PID: 0 at kernel/jump_label.c:166 static_key_enable_cpuslocked+0xfc/0x120 ... NIP static_key_enable_cpuslocked+0xfc/0x120 LR static_key_enable_cpuslocked+0xf8/0x120 Call Trace: static_key_enable_cpuslocked+0xf8/0x120 (unreliable) static_key_enable+0x30/0x50 setup_forced_irqthreads+0x28/0x40 do_early_param+0xa0/0x108 parse_args+0x290/0x4e0 parse_early_options+0x48/0x5c parse_early_param+0x58/0x84 early_init_devtree+0xd4/0x518 early_setup+0xb4/0x214 So call jump_label_init() just before parse_early_param() in early_init_devtree(). [mpe: Add call trace to change log and minor wording edits.]. EPSS estimates a 0.20% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: powerpc/64: Init jump labels before parse_early_param() On 64-bit, calling jump_label_init() in setup_feature_keys() is too late because static keys may be used in subroutines of parse_early_param() which is again subroutine of early_init_devtree(). For example booting with "threadirqs": static_key_enable_cpuslocked(): static key '0xc000000002953260' used before call to jump_label_init() WARNING: CPU: 0 PID: 0 at kernel/jump_label.c:166 static_key_enable_cpuslocked+0xfc/0x120 ... NIP static_key_enable_cpuslocked+0xfc/0x120 LR static_key_enable_cpuslocked+0xf8/0x120 Call Trace: static_key_enable_cpuslocked+0xf8/0x120 (unreliable) static_key_enable+0x30/0x50 setup_forced_irqthreads+0x28/0x40 do_early_param+0xa0/0x108 parse_args+0x290/0x4e0 parse_early_options+0x48/0x5c parse_early_param+0x58/0x84 early_init_devtree+0xd4/0x518 early_setup+0xb4/0x214 So call jump_label_init() just before parse_early_param() in early_init_devtree(). [mpe: Add call trace to change log and minor wording edits.]
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | < 4.9.326 |
| Linux | Linux Kernel | >= 4.10, < 4.14.291 |
| Linux | Linux Kernel | >= 4.15, < 4.19.256 |
| Linux | Linux Kernel | >= 4.20, < 5.4.211 |
| Linux | Linux Kernel | >= 5.5, < 5.10.138 |
| Linux | Linux Kernel | >= 5.11, < 5.15.63 |
| Linux | Linux Kernel | >= 5.16, < 5.19.4 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-50012?
How severe is CVE-2022-50012?
How do I fix CVE-2022-50012?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-50006In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50007In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50008In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50009In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50010In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50011In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50013In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50014In the Linux kernel, the following vulnerability has been re…7
- CVE-2022-50015In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50016In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50017In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50018Rejected reason: This CVE ID has been rejected or withdrawn …
Are you affected by CVE-2022-50012?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
