CVE-2026-97582: Linux kernel · hwmon: (gpio-fan) Fix use-after-free in alarm work
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e9fc7d53b2eb34c0a607d1659f49b46911aaf16c : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e9fc7d53b2eb34c0a607d1659f49b46911aaf16c, c6ab7f855891877a16d2e2ddf0cd0305fd098a85, a2471ed17b0e6ff7bfb6b2ea8e6e5b04c309d293 +4
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel commits identified by the fixedVersions hashes. Users should update to a Linux kernel version that includes these fixes. No additional mitigation is required once the kernel is updated.
Description
A use-after-free vulnerability in the Linux kernel's gpio-fan hwmon driver was fixed. The issue involved the fan_alarm_irq_handler queuing work that could run after the associated data structures were freed during device unbinding. This could lead to dereferencing freed memory. The fix replaced INIT_WORK() with devm_work_autocancel() to ensure proper cancellation of pending work before freeing resources.
References
- git.kernel.org/stable/c/594c62eea7c82f526054496e9fa9b895122a8016 (opens in a new tab)
- git.kernel.org/stable/c/6e67d9bdac810edacef78cbaeedd34445aa8ceb7 (opens in a new tab)
- git.kernel.org/stable/c/e9fc7d53b2eb34c0a607d1659f49b46911aaf16c (opens in a new tab)
- git.kernel.org/stable/c/9b12bd724db9db318e3a68be17693583dc29a066 (opens in a new tab)
- git.kernel.org/stable/c/30755d3a5782cd704c8921cac8ee66dffe4383ea (opens in a new tab)
- git.kernel.org/stable/c/c6ab7f855891877a16d2e2ddf0cd0305fd098a85 (opens in a new tab)
- git.kernel.org/stable/c/a2471ed17b0e6ff7bfb6b2ea8e6e5b04c309d293 (opens in a new tab)