CVE-2026-74547

hwmon: (adt7470) Fix busy-loop and I2C flooding in update thread

N/A
Published: August 15, 2026 at 12:27 PM UTC
Updated: August 19, 2026 at 05:21 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: hwmon: (adt7470) Fix busy-loop and I2C flooding in update thread When userspace configures 'auto_update_interval' to 0 via sysfs, the background kthread executes schedule_timeout_interruptible(0), which returns immediately. If 'num_temp_sensors' is concurrently or previously set to 0, the msleep_interruptible() delay inside adt7470_read_temperatures() also becomes 0. This combination forces the background thread into a tight, unbounded busy-loop, hogging the CPU and flooding the I2C bus with a continuous stream of transactions. Fix this vulnerability by raising the lower limit of the clamp_val in auto_update_interval_store() from 0 to 500 milliseconds. This guarantees a reasonable minimum sleep window between sensor updates, protecting the system from intentional or accidental I2C bus denial of service.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.29 ≤ v < 5.10.2652.6.29 ≤ v < 5.15.2162.6.29 ≤ v < 6.1.1832.6.29 ≤ v < 6.12.1032.6.29 ≤ v < 6.18.442.6.29 ≤ v < 6.6.1512.6.29 ≤ v < 7.1.82.6.29 ≤ v < 7.22.6.2989fac11cb3e7c5860c425dba14845c09ccede39d
Vendor states this is fixed in 1325975a2eab265510e6036d8bf0c0068373d332 (fixed)
Vendor states this is fixed in 1a42bd72a66205e439db1d1142442b62d393408a (fixed)
Vendor states this is fixed in 2c4c4d7cadd10b50b5489183bbbb9eb95f6f8344 (fixed)
Vendor states this is fixed in 38e6b5ce5794ff09442231cc171c2be5e900bab3 (fixed)
Vendor states this is fixed in 4dc1518f9cc57c6db99514cafeb02dd7117d5bda (fixed)
Vendor states this is fixed in 5ea299c3aa42a827f6a863eeead6de3525bbb17a (fixed)
Vendor states this is fixed in 82d65f7ef11edcea0228745440b8b4b1f222c34c (fixed)
Vendor states this is fixed in cb0b7f9c43b0abbd422a7e4c2c85e91db429207c (fixed)
Vendor states this is fixed in 2.6.29 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.6.151 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card