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-64038hwmon: (lm90) Stop work before releasing hwmon device

Description

In the Linux kernel, the following vulnerability has been resolved: hwmon: (lm90) Stop work before releasing hwmon device Sashiko reports: In lm90_probe(), the devm action to cancel the alert_work and report_work (lm90_restore_conf) is registered in lm90_init_client() before devm_hwmon_device_register_with_info() is called. Because devm executes cleanup actions in reverse order during module unbind or probe failure, the hwmon device is unregistered and freed first. If lm90_alert_work() or lm90_report_alarms() runs in the window between the hwmon device being freed and the delayed works being cancelled, lm90_update_alarms() will dereference the freed data->hwmon_dev here. Fix the problem by canceling the workers separately after registering the hwmon device and before registering the interrupt handler. This ensures that the workers are canceled after interrupts are disabled and before the hwmon device is released. Add "shutdown" flag to indicate that device shutdown is in progress to prevent workers from being re-armed.

Timeline

  1. ID reserved

    By Linux

  2. Published

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

CVSS scores of CVE-2026-64038, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.09% · top 100% of all CVEs (15 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected f6d0775119fb905fb02eafa98d575cf8ee792d46 – < 1decb2c1762f77910de787fbf9b3afb40cc1d646
    • affected f6d0775119fb905fb02eafa98d575cf8ee792d46 – < 1fe96176636cb17906680c098688b144bd9c1c45
    • affected f6d0775119fb905fb02eafa98d575cf8ee792d46 – < 5c116abf208dd97c4ceb76c5c50c9bc34a017796
    • affected f6d0775119fb905fb02eafa98d575cf8ee792d46 – < c98107817b0f6cdf51adc5e84e75c39ee25d8b28
    • affected f6d0775119fb905fb02eafa98d575cf8ee792d46 – < 479e297526aeb19c745eac5c1897f455f83dc5f8
    • affected f6d0775119fb905fb02eafa98d575cf8ee792d46 – < b09a45601094c7f4ec4db8090b825fa61e169d93
  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • 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-64038 badge
[![CVE-2026-64038](https://cveledger.app/badge/CVE-2026-64038.svg)](https://cveledger.app/cve/CVE-2026-64038)

Record last updated .