CVE-2026-64213: Linux kernel · hwmon: (lm90) Add lock protection to lm90_alert
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in bed1fc32e0eb653806fa98afcf55f9a311fc4ce2 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 15:59 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in bed1fc32e0eb653806fa98afcf55f9a311fc4ce2, b0b66aae8a94c3663d47e4000b0e81b89ce32186, 873e919e3101063a7a75989510ccfc125a4391cf +2
Exploitation evidence
Disclosed: evidence found.
CVE published 24 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: hwmon: (lm90) Add lock protection to lm90_alert Sashiko reports: lm90_alert() executes in the smbus alert context and calls lm90_update_confreg() to disable the hardware alert line, without acquiring hwmon_lock. Concurrently, sysfs write operations (such as lm90_write_convrate) hold the hwmon_lock, temporarily modify data->config, and then restore it. If an alert interrupt occurs concurrently with a sysfs write, the sysfs path will overwrite the alert handler's modifications to data->config and the hardware register. This unintentionally re-enables the hardware alert line while the alarm is still active, causing an interrupt storm. Add the missing lock to lm90_alert() to solve the problem.
References
- git.kernel.org/stable/c/02b88fa993582b4fe228b4143b330b0bb9f28353 (opens in a new tab)
- git.kernel.org/stable/c/165ef777ec6f634a5e4b8d9b0dadca8ef91fa90e (opens in a new tab)
- git.kernel.org/stable/c/bed1fc32e0eb653806fa98afcf55f9a311fc4ce2 (opens in a new tab)
- git.kernel.org/stable/c/b0b66aae8a94c3663d47e4000b0e81b89ce32186 (opens in a new tab)
- git.kernel.org/stable/c/873e919e3101063a7a75989510ccfc125a4391cf (opens in a new tab)