# thermal: intel_powerclamp: Use get_cpu() instead of smp_processor_id() to avoid crash

CVE record · `CVE-2022-50494`

- **Identifiers:** `CVE-2022-50494`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 4 Oct 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 4 Oct 2025, 15:43 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `d6d71ee4a14ae602db343ec48c491851d7ec5267 to before 3e799e815097febbcb81b472285be824f5d089f9` (git)
  - affected: `d6d71ee4a14ae602db343ec48c491851d7ec5267 to before 0f91f66c568b316b19cb042cf50584467b3bdff4` (git)
  - affected: `d6d71ee4a14ae602db343ec48c491851d7ec5267 to before 6904727db0eb62fb0c2dce1cf331c341d97ee4b7` (git)
  - affected: `d6d71ee4a14ae602db343ec48c491851d7ec5267 to before 5a646c38f648185ee2c62f2a19da3c6f04e27612` (git)
  - affected: `d6d71ee4a14ae602db343ec48c491851d7ec5267 to before 513943bf879d45005213e6f5cfb7d9e9943f589f` (git)
  - affected: `d6d71ee4a14ae602db343ec48c491851d7ec5267 to before 5614908434451aafbf9b24cb5247cf1d21269f76` (git)
  - affected: `d6d71ee4a14ae602db343ec48c491851d7ec5267 to before 6e2a347b304224b2aeb1c0ea000d1cf8a02cc592` (git)
  - affected: `d6d71ee4a14ae602db343ec48c491851d7ec5267 to before 418fae0700e85a498062424f8656435c32cdb200` (git)
  - affected: `d6d71ee4a14ae602db343ec48c491851d7ec5267 to before 68b99e94a4a2db6ba9b31fe0485e057b9354a640` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `3.9`
  - unaffected: `before 3.9` (semver)
  - unaffected: `4.9.331 to 4.9.*, inclusive` (semver)
  - unaffected: `4.14.296 to 4.14.*, inclusive` (semver)
  - unaffected: `4.19.262 to 4.19.*, inclusive` (semver)
  - unaffected: `5.4.220 to 5.4.*, inclusive` (semver)
  - unaffected: `5.10.150 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.75 to 5.15.*, inclusive` (semver)
  - unaffected: `5.19.17 to 5.19.*, inclusive` (semver)
  - unaffected: `6.0.3 to 6.0.*, inclusive` (semver)
  - unaffected: `6.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0016, the 5th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 4 Oct 2025, 15:43 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-50494)
- 4 Oct 2025, 16:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-50494)

## Sources

- [CVE List: CVE-2022-50494](https://www.cve.org/CVERecord?id=CVE-2022-50494)
- [NVD: CVE-2022-50494](https://nvd.nist.gov/vuln/detail/CVE-2022-50494)

### References from the CNA

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

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2022-50494>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2022-50494/>. Everything for agents: <https://agentprime.io/llms.txt>.
