Bug 2506799 (CVE-2026-64213) - CVE-2026-64213 kernel: hwmon: (lm90) Add lock protection to lm90_alert
Summary: CVE-2026-64213 kernel: hwmon: (lm90) Add lock protection to lm90_alert
Keywords:
Status: NEW
Alias: CVE-2026-64213
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-07-24 16:03 UTC by OSIDB Bzimport
Modified: 2026-07-28 10:20 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-07-24 16:03:52 UTC
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.

Comment 1 Mauro Matteo Cascella 2026-07-28 10:17:38 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026072414-CVE-2026-64213-dfb0@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.