VulnerabilityPublished 24 Jul 2026Updated 30 Oct 2026

CVE-2026-64213: Linux kernel · hwmon: (lm90) Add lock protection to lm90_alert

Source GCVE Database

Authoritative record:CVE-2026-64213· Medium

Not known to be exploited · CVSS 5.5 Medium · fixed in bed1fc32e0eb653806fa98afcf55f9a311fc4ce2 : update Linux kernel when convenient.

Data as of 30 Oct 2026, 16:33 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

Patch: Available – fixed in bed1fc32e0eb653806fa98afcf55f9a311fc4ce2, b0b66aae8a94c3663d47e4000b0e81b89ce32186, 873e919e3101063a7a75989510ccfc125a4391cf +3

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-mf77-wwf7-m2ff

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 7a1d220ccb0cc2b808eb176fb05bf55a38179f3f, < bed1fc32e0eb653806fa98afcf55f9a311fc4ce2	Fixed in bed1fc32e0eb653806fa98afcf55f9a311fc4ce2
LinuxLinux	Affected ≥ 7a1d220ccb0cc2b808eb176fb05bf55a38179f3f, < b0b66aae8a94c3663d47e4000b0e81b89ce32186	Fixed in b0b66aae8a94c3663d47e4000b0e81b89ce32186
LinuxLinux	Affected ≥ 7a1d220ccb0cc2b808eb176fb05bf55a38179f3f, < 873e919e3101063a7a75989510ccfc125a4391cf	Fixed in 873e919e3101063a7a75989510ccfc125a4391cf
LinuxLinux	Affected ≥ 7a1d220ccb0cc2b808eb176fb05bf55a38179f3f, < 165ef777ec6f634a5e4b8d9b0dadca8ef91fa90e	Fixed in 165ef777ec6f634a5e4b8d9b0dadca8ef91fa90e
LinuxLinux	Affected ≥ 7a1d220ccb0cc2b808eb176fb05bf55a38179f3f, < 02b88fa993582b4fe228b4143b330b0bb9f28353	Fixed in 02b88fa993582b4fe228b4143b330b0bb9f28353
LinuxLinux	Affected ≥ 7a1d220ccb0cc2b808eb176fb05bf55a38179f3f, < 1dc6a3469b5427e3bfd19010d7755ebc6019abc1	Fixed in 1dc6a3469b5427e3bfd19010d7755ebc6019abc1

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

Community reviews

Loading reviews…