Answer in brief
CVE-2026-74547 records a Unknown severity vulnerability in hwmon: (adt7470) Fix busy-loop and I2C flooding in update thread. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=89fac11cb3e7c5860c425dba14845c09ccede39d <1a42bd72a66205e439db1d1142442b62d393408a || >=89fac11cb3e7c5860c425dba14845c09ccede39d <38e6b5ce5794ff09442231cc171c2be5e900bab3 || >=89fac11cb3e7c5860c425dba14845c09ccede39d <82d65f7ef11edcea0228745440b8b4b1f222c34c || >=89fac11cb3e7c5860c425dba14845c09ccede39d <5ea299c3aa42a827f6a863eeead6de3525bbb17a || >=89fac11cb3e7c5860c425dba14845c09ccede39d <cb0b7f9c43b0abbd422a7e4c2c85e91db429207c | 1a42bd72a66205e439db1d1142442b62d393408a, 38e6b5ce5794ff09442231cc171c2be5e900bab3, 82d65f7ef11edcea0228745440b8b4b1f222c34c, 5ea299c3aa42a827f6a863eeead6de3525bbb17a, cb0b7f9c43b0abbd422a7e4c2c85e91db429207c |
| Linux/Linuxgeneric | 2.6.29 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-74547 records a Unknown severity vulnerability in hwmon: (adt7470) Fix busy-loop and I2C flooding in update thread. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=89fac11cb3e7c5860c425dba14845c09ccede39d <1a42bd72a66205e439db1d1142442b62d393408a || >=89fac11cb3e7c5860c425dba14845c09ccede39d <38e6b5ce5794ff09442231cc171c2be5e900bab3 || >=89fac11cb3e7c5860c425dba14845c09ccede39d <82d65f7ef11edcea0228745440b8b4b1f222c34c || >=89fac11cb3e7c5860c425dba14845c09ccede39d <5ea299c3aa42a827f6a863eeead6de3525bbb17a || >=89fac11cb3e7c5860c425dba14845c09ccede39d <cb0b7f9c43b0abbd422a7e4c2c85e91db429207c | 1a42bd72a66205e439db1d1142442b62d393408a, 38e6b5ce5794ff09442231cc171c2be5e900bab3, 82d65f7ef11edcea0228745440b8b4b1f222c34c, 5ea299c3aa42a827f6a863eeead6de3525bbb17a, cb0b7f9c43b0abbd422a7e4c2c85e91db429207c |
| Linux/Linuxgeneric | 2.6.29 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.