Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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 ]

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 13 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-50494, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected d6d71ee4a14ae602db343ec48c491851d7ec5267 – < 3e799e815097febbcb81b472285be824f5d089f9
    • affected d6d71ee4a14ae602db343ec48c491851d7ec5267 – < 0f91f66c568b316b19cb042cf50584467b3bdff4
    • affected d6d71ee4a14ae602db343ec48c491851d7ec5267 – < 6904727db0eb62fb0c2dce1cf331c341d97ee4b7
    • affected d6d71ee4a14ae602db343ec48c491851d7ec5267 – < 5a646c38f648185ee2c62f2a19da3c6f04e27612
    • affected d6d71ee4a14ae602db343ec48c491851d7ec5267 – < 513943bf879d45005213e6f5cfb7d9e9943f589f
    • affected d6d71ee4a14ae602db343ec48c491851d7ec5267 – < 5614908434451aafbf9b24cb5247cf1d21269f76
    • affected d6d71ee4a14ae602db343ec48c491851d7ec5267 – < 6e2a347b304224b2aeb1c0ea000d1cf8a02cc592
    • affected d6d71ee4a14ae602db343ec48c491851d7ec5267 – < 418fae0700e85a498062424f8656435c32cdb200
    • affected d6d71ee4a14ae602db343ec48c491851d7ec5267 – < 68b99e94a4a2db6ba9b31fe0485e057b9354a640
  • Linux · Linux

    • affected 3.9
    • unaffected < 3.9
    • unaffected 4.9.331 – ≤ 4.9.*
    • unaffected 4.14.296 – ≤ 4.14.*
    • unaffected 4.19.262 – ≤ 4.19.*
    • unaffected 5.4.220 – ≤ 5.4.*
    • unaffected 5.10.150 – ≤ 5.10.*
    • unaffected 5.15.75 – ≤ 5.15.*
    • unaffected 5.19.17 – ≤ 5.19.*
    • unaffected 6.0.3 – ≤ 6.0.*
    • unaffected 6.1 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-50494 badge
[![CVE-2022-50494](https://cveledger.app/badge/CVE-2022-50494.svg)](https://cveledger.app/cve/CVE-2022-50494)

Record last updated .