Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 4 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

CVSS scores of CVE-2026-64213, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 7a1d220ccb0cc2b808eb176fb05bf55a38179f3f – < 1dc6a3469b5427e3bfd19010d7755ebc6019abc1
    • affected 7a1d220ccb0cc2b808eb176fb05bf55a38179f3f – < 02b88fa993582b4fe228b4143b330b0bb9f28353
    • affected 7a1d220ccb0cc2b808eb176fb05bf55a38179f3f – < 165ef777ec6f634a5e4b8d9b0dadca8ef91fa90e
    • affected 7a1d220ccb0cc2b808eb176fb05bf55a38179f3f – < bed1fc32e0eb653806fa98afcf55f9a311fc4ce2
    • affected 7a1d220ccb0cc2b808eb176fb05bf55a38179f3f – < b0b66aae8a94c3663d47e4000b0e81b89ce32186
    • affected 7a1d220ccb0cc2b808eb176fb05bf55a38179f3f – < 873e919e3101063a7a75989510ccfc125a4391cf
  • Linux · Linux

    • affected 5.3
    • unaffected < 5.3
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.34 – ≤ 6.18.*
    • unaffected 7.0.11 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64213 badge
[![CVE-2026-64213](https://cveledger.app/badge/CVE-2026-64213.svg)](https://cveledger.app/cve/CVE-2026-64213)

Record last updated .