| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Linux Kernel up to 6.0.2 and classified as critical. Affected by this issue is the function get_cpu of the component thermal. Performing a manipulation results in injection.
This vulnerability is identified as CVE-2022-50494. There is not any exploit available.
The affected component should be upgraded.
Details
A vulnerability classified as critical has been found in Linux Kernel up to 6.0.2. This affects the function get_cpu of the component thermal. The manipulation with an unknown input leads to a injection vulnerability. CWE is classifying the issue as CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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 ]
The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2022-50494 since 10/04/2025. The exploitability is told to be difficult. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/01/2026). MITRE ATT&CK project uses the attack technique T1055 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 279908 (SUSE SLES12 Security Update : kernel (SUSE-SU-2025:4515-1)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 4.9.331, 4.14.296, 4.19.262, 5.4.220, 5.10.150, 5.15.75, 5.19.17 or 6.0.3 eliminates this vulnerability. Applying the patch 3e799e815097febbcb81b472285be824f5d089f9/0f91f66c568b316b19cb042cf50584467b3bdff4/6904727db0eb62fb0c2dce1cf331c341d97ee4b7/5a646c38f648185ee2c62f2a19da3c6f04e27612/513943bf879d45005213e6f5cfb7d9e9943f589f/5614908434451aafbf9b24cb5247cf1d21269f76/6e2a347b304224b2aeb1c0ea000d1cf8a02cc592/418fae0700e85a498062424f8656435c32cdb200/68b99e94a4a2db6ba9b31fe0485e057b9354a640 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (279908) and CERT Bund (WID-SEC-2025-2194). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Google Container-Optimized OS
- Debian Linux
- Google Cloud Platform
- Amazon Linux 2
- Red Hat Enterprise Linux
- Ubuntu Linux
- SUSE Linux
- Oracle Linux
- SUSE openSUSE
- Open Source Linux Kernel
- RESF Rocky Linux
- NetApp ActiveIQ Unified Manager
- IBM QRadar SIEM
- Dell NetWorker
Product
Type
Vendor
Name
Version
- 4.9.330
- 4.14.295
- 4.19.261
- 5.4.219
- 5.10.149
- 5.15.0
- 5.15.1
- 5.15.2
- 5.15.3
- 5.15.4
- 5.15.5
- 5.15.6
- 5.15.7
- 5.15.8
- 5.15.9
- 5.15.10
- 5.15.11
- 5.15.12
- 5.15.13
- 5.15.14
- 5.15.15
- 5.15.16
- 5.15.17
- 5.15.18
- 5.15.19
- 5.15.20
- 5.15.21
- 5.15.22
- 5.15.23
- 5.15.24
- 5.15.25
- 5.15.26
- 5.15.27
- 5.15.28
- 5.15.29
- 5.15.30
- 5.15.31
- 5.15.32
- 5.15.33
- 5.15.34
- 5.15.35
- 5.15.36
- 5.15.37
- 5.15.38
- 5.15.39
- 5.15.40
- 5.15.41
- 5.15.42
- 5.15.43
- 5.15.44
- 5.15.45
- 5.15.46
- 5.15.47
- 5.15.48
- 5.15.49
- 5.15.50
- 5.15.51
- 5.15.52
- 5.15.53
- 5.15.54
- 5.15.55
- 5.15.56
- 5.15.57
- 5.15.58
- 5.15.59
- 5.15.60
- 5.15.61
- 5.15.62
- 5.15.63
- 5.15.64
- 5.15.65
- 5.15.66
- 5.15.67
- 5.15.68
- 5.15.69
- 5.15.70
- 5.15.71
- 5.15.72
- 5.15.73
- 5.15.74
- 5.19.0
- 5.19.1
- 5.19.2
- 5.19.3
- 5.19.4
- 5.19.5
- 5.19.6
- 5.19.7
- 5.19.8
- 5.19.9
- 5.19.10
- 5.19.11
- 5.19.12
- 5.19.13
- 5.19.14
- 5.19.15
- 5.19.16
- 6.0.0
- 6.0.1
- 6.0.2
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 4.9
VulDB Base Score: 4.6
VulDB Temp Score: 4.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: InjectionCWE: CWE-74 / CWE-707 / CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 279908
Nessus Name: SUSE SLES12 Security Update : kernel (SUSE-SU-2025:4515-1)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 4.9.331/4.14.296/4.19.262/5.4.220/5.10.150/5.15.75/5.19.17/6.0.3
Patch: 3e799e815097febbcb81b472285be824f5d089f9/0f91f66c568b316b19cb042cf50584467b3bdff4/6904727db0eb62fb0c2dce1cf331c341d97ee4b7/5a646c38f648185ee2c62f2a19da3c6f04e27612/513943bf879d45005213e6f5cfb7d9e9943f589f/5614908434451aafbf9b24cb5247cf1d21269f76/6e2a347b304224b2aeb1c0ea000d1cf8a02cc592/418fae0700e85a498062424f8656435c32cdb200/68b99e94a4a2db6ba9b31fe0485e057b9354a640
Timeline
10/04/2025 Advisory disclosed10/04/2025 CVE reserved
10/04/2025 VulDB entry created
03/01/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2022-50494 (🔒)
GCVE (CVE): GCVE-0-2022-50494
GCVE (VulDB): GCVE-100-327141
CERT Bund: WID-SEC-2025-2194 - Linux Kernel: Mehrere Schwachstellen
Entry
Created: 10/04/2025 20:23Updated: 03/01/2026 18:57
Changes: 10/04/2025 20:23 (59), 11/23/2025 08:28 (7), 12/26/2025 07:37 (1), 12/26/2025 14:29 (2), 01/24/2026 12:05 (12), 03/01/2026 18:57 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.

No comments yet. Languages: en.
Please log in to comment.