# hwmon: (lm90) Add lock protection to lm90_alert

CVE record · `CVE-2026-64213`

- **Identifiers:** `CVE-2026-64213`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 24 Jul 2026
- **Updated:** 6 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 24 Jul 2026, 15:23 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: `7a1d220ccb0cc2b808eb176fb05bf55a38179f3f to before 1dc6a3469b5427e3bfd19010d7755ebc6019abc1` (git)
  - affected: `7a1d220ccb0cc2b808eb176fb05bf55a38179f3f to before 02b88fa993582b4fe228b4143b330b0bb9f28353` (git)
  - affected: `7a1d220ccb0cc2b808eb176fb05bf55a38179f3f to before 165ef777ec6f634a5e4b8d9b0dadca8ef91fa90e` (git)
  - affected: `7a1d220ccb0cc2b808eb176fb05bf55a38179f3f to before bed1fc32e0eb653806fa98afcf55f9a311fc4ce2` (git)
  - affected: `7a1d220ccb0cc2b808eb176fb05bf55a38179f3f to before b0b66aae8a94c3663d47e4000b0e81b89ce32186` (git)
  - affected: `7a1d220ccb0cc2b808eb176fb05bf55a38179f3f to before 873e919e3101063a7a75989510ccfc125a4391cf` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.3`
  - unaffected: `before 5.3` (semver)
  - unaffected: `6.1.191 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.160 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.114 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.34 to 6.18.*, inclusive` (semver)
  - unaffected: `7.0.11 to 7.0.*, inclusive` (semver)
  - unaffected: `7.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel's lm90 hardware monitoring driver is affected in versions from 5.3 up to the fixes listed in the source, with 5.3 and later kernels before the fixed releases included. A race between the SMBus alert handler and sysfs writes could re-enable the alert line while an alarm is still active, causing an interrupt storm. The source gives few details on how an attacker would trigger it. Upgrade to a fixed kernel version: 6.1.191 or later in the 6.1 series, 6.6.160 or later in 6.6, 6.12.114 or later in 6.12, or 6.18.34 or later in 6.18.

Written 12 Nov 2026.

## 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.0012, the 2nd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 24 Jul 2026, 15:23 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-64213)
- 24 Jul 2026, 16:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-64213)

## Sources

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

### References from the CNA

- <https://git.kernel.org/stable/c/1dc6a3469b5427e3bfd19010d7755ebc6019abc1>
- <https://git.kernel.org/stable/c/02b88fa993582b4fe228b4143b330b0bb9f28353>
- <https://git.kernel.org/stable/c/165ef777ec6f634a5e4b8d9b0dadca8ef91fa90e>
- <https://git.kernel.org/stable/c/bed1fc32e0eb653806fa98afcf55f9a311fc4ce2>
- <https://git.kernel.org/stable/c/b0b66aae8a94c3663d47e4000b0e81b89ce32186>
- <https://git.kernel.org/stable/c/873e919e3101063a7a75989510ccfc125a4391cf>

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-2026-64213>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

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