0.0
NA
CVE-2026-64213
hwmon: (lm90) Add lock protection to lm90_alert
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.

INFO

Published Date :

July 24, 2026, 4:16 p.m.

Last Modified :

July 24, 2026, 4:16 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2026-64213 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

Solution
Add locking to lm90_alert to prevent concurrent modification issues.
  • Acquire hwmon_lock in lm90_alert.
  • Ensure lm90_alert protects data->config.
  • Review other smbus alert handlers for similar issues.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-64213.

URL Resource
https://git.kernel.org/stable/c/873e919e3101063a7a75989510ccfc125a4391cf
https://git.kernel.org/stable/c/b0b66aae8a94c3663d47e4000b0e81b89ce32186
https://git.kernel.org/stable/c/bed1fc32e0eb653806fa98afcf55f9a311fc4ce2
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-64213 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-64213 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-64213 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-64213 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Jul. 24, 2026

    Action Type Old Value New Value
    Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '7a1d220ccb0cc2b808eb176fb05bf55a38179f3f', 'lessThan': 'bed1fc32e0eb653806fa98afcf55f9a311fc4ce2', 'versionType': 'git'}, {'status': 'affected', 'version': '7a1d220ccb0cc2b808eb176fb05bf55a38179f3f', 'lessThan': 'b0b66aae8a94c3663d47e4000b0e81b89ce32186', 'versionType': 'git'}, {'status': 'affected', 'version': '7a1d220ccb0cc2b808eb176fb05bf55a38179f3f', 'lessThan': '873e919e3101063a7a75989510ccfc125a4391cf', 'versionType': 'git'}], 'programFiles': ['drivers/hwmon/lm90.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '5.3'}, {'status': 'unaffected', 'version': '0', 'lessThan': '5.3', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.18.34', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.11', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/hwmon/lm90.c'], 'defaultStatus': 'affected'}]
    Added 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.
    Added Reference https://git.kernel.org/stable/c/873e919e3101063a7a75989510ccfc125a4391cf
    Added Reference https://git.kernel.org/stable/c/b0b66aae8a94c3663d47e4000b0e81b89ce32186
    Added Reference https://git.kernel.org/stable/c/bed1fc32e0eb653806fa98afcf55f9a311fc4ce2
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.