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

Published Jul 24, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

hwmon: (lm90) Add lock protection to lm90alert

Sashiko reports:

lm90alert() executes in the smbus alert context and calls lm90updateconfreg() to disable the hardware alert line, without acquiring hwmonlock.

Concurrently, sysfs write operations (such as lm90writeconvrate) hold the hwmonlock, 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 lm90alert() to solve the problem.

Affected Software

6 affected components
Linux Linux kernel
Linux Linux kernel>=5.3<6.18.34
Linux Linux kernel>=6.19<7.0.11
Linux Linux kernel=7.1-rc1
Linux Linux kernel=7.1-rc2
Linux Linux kernel=7.1-rc3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Modify lm90_alert() to acquire hwmon_lock before calling lm90_update_confreg() (which disables the hardware alert line), temporarily modify data->config while the lock is held, and then restore the original data->config before releasing hwmon_lock to prevent sysfs write operations from overwriting alert-handler modifications and causing an interrupt storm.

    Linux kernel hwmon (lm90) lm90_alert() locking = Add lock protection using hwmon_lock around temporary updates to data->config (disable hardware alert line via lm90_update_confreg(), then restore data->config)

Event History

Jul 24, 2026
CVE Published
via MITRE·03:23 PM
Data Sourced
via MITRE·03:23 PM
Description
Data Sourced
via NVD·04:16 PM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-64213?

The severity of CVE-2026-64213 is medium with a score of 5.5 according to CVSS 3.1.

2

How do I fix CVE-2026-64213?

To fix CVE-2026-64213, you need to update to the patched version of the Linux kernel where the vulnerability has been addressed.

3

What systems are affected by CVE-2026-64213?

CVE-2026-64213 affects systems running the vulnerable versions of the Linux kernel that include the hwmon lm90 driver.

4

What type of vulnerability is CVE-2026-64213?

CVE-2026-64213 is a locking issue in the hwmon subsystem of the Linux kernel, specifically related to concurrent access.

5

What are the potential consequences of CVE-2026-64213?

The potential consequence of CVE-2026-64213 includes denial of service (DoS) due to improper handling of hardware alerts.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203