CVE-2026-98197

Description

A flaw was found in the Linux kernel's w83791d hardware monitoring driver. This vulnerability allows a local user to cause a Denial of Service (DoS) by triggering a kernel crash. During driver removal, the driver fails to unregister optional sysfs interface files, leaving them accessible after the underlying device data has been released. An unprivileged or local user interacting with these leftover files causes the kernel to access freed memory, resulting in a use-after-free condition.

Statement

This flaw is rated as having Moderate severity rather than Important because exploitation requires local access, specific hardware monitoring hardware, and an uncommon operational state where the driver is unbound during active sysfs access. Red Hat Enterprise Linux does not load the w83791d kernel module by default unless the corresponding Winbond hardware sensor is physically present on the system. Under vulnerable conditions, triggering the dangling sysfs access can cause a kernel panic, resulting in a local denial of service.

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 HatNVDcve.org
Base Score7N/A7
Attack VectorLocalN/ALocal
Attack ComplexityHighN/AHigh
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityHighN/AHigh
Integrity ImpactHighN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

cve.org: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/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

Want to get errata notifications? Sign up here.