5.5

CVE-2022-50494: linux

CVSS: 5.5v3.1MediumAnalyzed
AliasesUBUNTU-CVE-2022-50494DEBIAN-CVE-2022-50494
Published 04-10-2025Last modified 11-05-2026

Vulnerability summary

CVE-2022-50494 is a medium (CVSS 5.5) vulnerability in linux. EPSS estimates a 0.16% chance of exploitation in the next 30 days, higher than 4.7% of scored vulnerabilities.

Overall risk
22/100
0100
Low · default modelHow is this calculated?
CVSS score
5.5/10
010
Medium · v3.1 (NVD)
EPSS score
0.16%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 8 · Related 7

Timeline

  1. 04-10-2025
    PublishedVulnerability first disclosed.
  2. 11-05-2026
    Last modifiedVulnerability information updated.

Description

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 ]

CVSS metrics

3 scores · 3 sources · 1 version

EPSS trend

Probability

0.16%

Chance of exploitation in the next 30 days

Percentile

5%

Versus all other CVEs

30-day change

0.00 pp

From 0.16% on 21-09-2026

21-09-202621-10-2026
EPSS score
0.16%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

No weakness data has been published for this record.

Affected systems

Ubuntu120 products
  • linuxAll versions (No fix recorded) | < 4.15.0-204.215 | < 5.4.0-139.156 | < 5.15.0-60.66
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-awsAll versions (No fix recorded) | < 4.15.0-1150.163 | < 5.4.0-1096.104 | < 5.15.0-1030.34
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Linux2 products
  • linux≥ d6d71ee4a14ae602db343ec48c491851d7ec5267, < 3e799e815097febbcb81b472285be824f5d089f9 | ≥ d6d71ee4a14ae602db343ec48c491851d7ec5267, < 0f91f66c568b316b19cb042cf50584467b3bdff4 | ≥ d6d71ee4a14ae602db343ec48c491851d7ec5267, < 6904727db0eb62fb0c2dce1cf331c341d97ee4b7 | ≥ d6d71ee4a14ae602db343ec48c491851d7ec5267, < 5a646c38f648185ee2c62f2a19da3c6f04e27612 | ≥ d6d71ee4a14ae602db343ec48c491851d7ec5267, < 513943bf879d45005213e6f5cfb7d9e9943f589f | ≥ d6d71ee4a14ae602db343ec48c491851d7ec5267, < 5614908434451aafbf9b24cb5247cf1d21269f76 | ≥ d6d71ee4a14ae602db343ec48c491851d7ec5267, < 6e2a347b304224b2aeb1c0ea000d1cf8a02cc592 | ≥ d6d71ee4a14ae602db343ec48c491851d7ec5267, < 418fae0700e85a498062424f8656435c32cdb200 | ≥ d6d71ee4a14ae602db343ec48c491851d7ec5267, < 68b99e94a4a2db6ba9b31fe0485e057b9354a640 | 3.9
  • linux_kernel≥ 3.9, < 4.9.331 | ≥ 4.10, < 4.14.296 | ≥ 4.15, < 4.19.262 | ≥ 4.20, < 5.4.220 | ≥ 5.5, < 5.10.150 | ≥ 5.11, < 5.15.75 | ≥ 5.16, < 5.19.17 | ≥ 6.0, < 6.0.3
Debian1 product
  • linux< 6.0.3-1

3 vendors · 123 products

References

13 links
Show all 13 references