CVE-2026-74547hwmon: (adt7470) Fix busy-loop and I2C flooding in update thread
- —Not scoredno CVSS score yet
- 0.18%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.18% · top 93% of all CVEs (13 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 89fac11cb3e7c5860c425dba14845c09ccede39d – < 2c4c4d7cadd10b50b5489183bbbb9eb95f6f8344
- affected 89fac11cb3e7c5860c425dba14845c09ccede39d – < 4dc1518f9cc57c6db99514cafeb02dd7117d5bda
- affected 89fac11cb3e7c5860c425dba14845c09ccede39d – < 1325975a2eab265510e6036d8bf0c0068373d332
- affected 89fac11cb3e7c5860c425dba14845c09ccede39d – < 1a42bd72a66205e439db1d1142442b62d393408a
- affected 89fac11cb3e7c5860c425dba14845c09ccede39d – < 38e6b5ce5794ff09442231cc171c2be5e900bab3
- affected 89fac11cb3e7c5860c425dba14845c09ccede39d – < 82d65f7ef11edcea0228745440b8b4b1f222c34c
- affected 89fac11cb3e7c5860c425dba14845c09ccede39d – < 5ea299c3aa42a827f6a863eeead6de3525bbb17a
- affected 89fac11cb3e7c5860c425dba14845c09ccede39d – < cb0b7f9c43b0abbd422a7e4c2c85e91db429207c
- affected 2.6.29
- unaffected < 2.6.29
- unaffected 5.10.265 – ≤ 5.10.*
- unaffected 5.15.216 – ≤ 5.15.*
- unaffected 6.1.183 – ≤ 6.1.*
- unaffected 6.6.151 – ≤ 6.6.*
- unaffected 6.12.103 – ≤ 6.12.*
- unaffected 6.18.44 – ≤ 6.18.*
- unaffected 7.1.8 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References8
- https://git.kernel.org/stable/c/2c4c4d7cadd10b50b5489183bbbb9eb95f6f8344 (opens in a new tab)
- https://git.kernel.org/stable/c/4dc1518f9cc57c6db99514cafeb02dd7117d5bda (opens in a new tab)
- https://git.kernel.org/stable/c/1325975a2eab265510e6036d8bf0c0068373d332 (opens in a new tab)
- https://git.kernel.org/stable/c/1a42bd72a66205e439db1d1142442b62d393408a (opens in a new tab)
- https://git.kernel.org/stable/c/38e6b5ce5794ff09442231cc171c2be5e900bab3 (opens in a new tab)
- https://git.kernel.org/stable/c/82d65f7ef11edcea0228745440b8b4b1f222c34c (opens in a new tab)
- https://git.kernel.org/stable/c/5ea299c3aa42a827f6a863eeead6de3525bbb17a (opens in a new tab)
- https://git.kernel.org/stable/c/cb0b7f9c43b0abbd422a7e4c2c85e91db429207c (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-59740 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-74547)Record last updated .