CVE Tools

CVE-2026-98197

hwmon: (w83791d) remove fan/pwm 4-5 sysfs group on remove

No known exploitation. EPSS puts it in the 2nd percentile. Fixed versions are out.

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • LinuxAffected: ≥ 6e1ecd9b8f1358ed4d099f0c54434240dc40debe, < 081e3a78453635fb370b1712809d2af29e60b4c5Upgrade to: 081e3a78453635fb370b1712809d2af29e60b4c5Affected: ≥ 6e1ecd9b8f1358ed4d099f0c54434240dc40debe, < b1d419eb3bc41245c3d3d99dfe1a7b6c45989586Upgrade to: b1d419eb3bc41245c3d3d99dfe1a7b6c45989586Affected: ≥ 6e1ecd9b8f1358ed4d099f0c54434240dc40debe, < 2ccf6c512290a288a2d4d7f076430dfb0c6ee476Upgrade to: 2ccf6c512290a288a2d4d7f076430dfb0c6ee476Affected: ≥ 6e1ecd9b8f1358ed4d099f0c54434240dc40debe, < f6e2ab72f32d16d71a2549c7ea062dd209f71670Upgrade to: f6e2ab72f32d16d71a2549c7ea062dd209f71670 + 4 more branchesStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

In the Linux kernel, the following vulnerability has been resolved: hwmon: (w83791d) remove fan/pwm 4-5 sysfs group on remove When the fan/pwm 4-5 pins are not used as GPIO, w83791d_probe() creates the w83791d_group_fanpwm45 sysfs group on the I2C client device. The probe error path removes this group when a later initialization step fails, but the normal remove path only removes w83791d_group. As a result, the optional fan/pwm 4-5 sysfs files can remain after the driver is unbound. The callbacks associated with these files access the driver data, which is devm allocated and released after driver unbind. Leaving the sysfs files behind can therefore result in accesses to stale driver data. Remove w83791d_group_fanpwm45 during normal teardown as well. This issue was found by manual code inspection.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS2nd
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.1% chance of exploitation activity in the next 30 days, which ranks it in the 2nd percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

3 events over 1 day, from the signal feeds we watch.

  1. Record updated
  2. Publishedrecord updated

Affected products

Technical detail

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

Scored 7.0 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Linux, not every advisory.