CVE-2026-97582
Description
A flaw was found in the Linux kernel's GPIO fan driver. When a device is unbound, pending alarm work is not properly canceled before associated memory resources are freed, resulting in a use-after-free condition. A local attacker could exploit this race condition to cause a Denial of Service (DoS) through a kernel crash or potentially achieve arbitrary code execution.
Statement
A flaw was found in the Linux kernel's GPIO fan (gpio-fan) hwmon driver. fan_alarm_irq_handler() queues fan_data->alarm_work, but nothing cancels that work when the device is unbound; devres cleanup frees the interrupt (which only waits for the handler itself) and then releases the hwmon device and fan_data, so a still-pending fan_alarm_notify() can run after those frees and dereference already-freed memory. Red Hat rates this flaw Moderate (CVSS 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H): a local attacker would need access to the affected host, the ability to trigger a device unbind, and to win the resulting race window, most plausibly crashing the kernel and causing a denial of service; arbitrary code execution is considered possible but has not been demonstrated.
Red Hat Enterprise Linux 10 (kernel) and Red Hat In-Vehicle OS 2 (kernel and kernel-ivos-qualcomm components) contain the vulnerable code and are marked affected with the fix deferred to a later update; while the fix is pending, the residual risk is limited because exploitation requires local access, privileges over device lifecycle operations, and winning a narrow race, with impact primarily on availability. Red Hat Enterprise Linux 6, 7, 8, and 9, including their Real Time kernel variants, and the OpenShift Container Platform RHEL CoreOS 8 and RHEL CoreOS 9 based images are not affected because the vulnerable code is not present in those streams.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Memory
If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.