CVE-2022-50494 [Medium] | Security Vulnerability in Linux Kernel

In the Linux kernel, the following vulnerability has been resolved: thermal: intel_powerclamp: Use get_cpu() instead of smp_processor_id() to avoid crash When CPU 0 is offline and intel_powerclamp is used to inject idle, it generates kernel BUG: BUG: using smp_processor_id() in preemptible [00000000] code: bash/15687 caller is debug_smp_processor_id+0x17/0x20 CPU: 4 PID: 15687 Comm: bash Not tainted 5.19.0-rc7+ #57 Call Trace: <TASK> dump_stack_lvl+0x49/0x63 dump_stack+0x10/0x16 check_preemption_disabled+0xdd/0xe0 debug_smp_processor_id+0x17/0x20 powerclamp_set_cur_state+0x7f/0xf9 [intel_powerclamp] ... ... Here CPU 0 is the control CPU by default and changed to the current CPU, if CPU 0 offlined. This check has to be performed under cpus_read_lock(), hence the above warning. Use get_cpu() instead of smp_processor_id() to avoid this BUG. [ rjw: Subject edits ]

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-10-05	—	0.03%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-10-05

—

0.03%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

3.6

[email protected]

OS Trackers for CVE-2022-50494

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-50494 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2022-50494
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2022-50494
`suse`	medium	—	https://www.suse.com/security/cve/CVE-2022-50494/
`ubuntu`	medium	CVE-2022-50494 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1414 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): DNE 1017, ignored 161, released 148, not-affected 82, needed 5, needs-triage 1.	https://ubuntu.com/security/CVE-2022-50494

Affected software / configurations for CVE-2022-50494

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 3.9, < 4.9.331	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.10, < 4.14.296	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.15, < 4.19.262	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.20, < 5.4.220	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.5, < 5.10.150	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.75	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 5.19.17	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.0, < 6.0.3	cpe:2.3:o:linux:linux_kernel::::::::

References for CVE-2022-50494

URL	Tags
https://git.kernel.org/stable/c/0f91f66c568b316b19cb042cf50584467b3bdff4	Patch
https://git.kernel.org/stable/c/3e799e815097febbcb81b472285be824f5d089f9	Patch
https://git.kernel.org/stable/c/418fae0700e85a498062424f8656435c32cdb200	Patch
https://git.kernel.org/stable/c/513943bf879d45005213e6f5cfb7d9e9943f589f	Patch
https://git.kernel.org/stable/c/5614908434451aafbf9b24cb5247cf1d21269f76	Patch
https://git.kernel.org/stable/c/5a646c38f648185ee2c62f2a19da3c6f04e27612	Patch
https://git.kernel.org/stable/c/68b99e94a4a2db6ba9b31fe0485e057b9354a640	Patch
https://git.kernel.org/stable/c/6904727db0eb62fb0c2dce1cf331c341d97ee4b7	Patch
https://git.kernel.org/stable/c/6e2a347b304224b2aeb1c0ea000d1cf8a02cc592	Patch

URL

CVE-2022-50494 | thermal: intel_powerclamp: Use get_cpu() instead of smp_processor_id() to avoid crash

Exploit prediction scoring system (EPSS) score for CVE-2022-50494

Common vulnerability scoring system (CVSS) metrics for CVE-2022-50494

Weakness enumeration for CVE-2022-50494

OS Trackers for CVE-2022-50494

Affected software / configurations for CVE-2022-50494

References for CVE-2022-50494