CVE-2026-98000: Linux Vulnerability

Description

In the Linux kernel, the following vulnerability has been resolved: hwmon: Fix potential UAF in pec_store Sashiko reports: In pec_store(), a guard(mutex)(&hwdev->lock) is taken. If the chip write operation returns an error other than -EOPNOTSUPP, the code jumps to the put label, which calls put_device(hdev). If this drops the final reference, the device is freed. When the function then returns, the guard cleanup function runs and attempts to unlock the freed mutex. Use scoped_guard() instead of guard() to avoid the problem.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

Vendor	Product	Versions
Linux	Linux	>= 3ad2a7b9b15d5072139a20be84adb36776eb6c9b, < 8afab57bcdbc2186f325972e777880ac5a220f4f; >= 3ad2a7b9b15d5072139a20be84adb36776eb6c9b, < 01dd8b4fc2cf83c66565c0f382fb1841e9000a89; >= 3ad2a7b9b15d5072139a20be84adb36776eb6c9b, < 354ccc99b2dc8ba0cf6d4de34e520bcf6ecca5c2
Linux	Linux	6.18

References

Timeline

Published: Sep 25, 2026
Last Modified: Sep 25, 2026
Status: Received

Frequently Asked Questions

What is CVE-2026-98000?

In the Linux kernel, the following vulnerability has been resolved: hwmon: Fix potential UAF in pec_store Sashiko reports: In pec_store(), a guard(mutex)(&hwdev->lock) is taken. If the chip write operation returns an error other than -EOPNOTSUPP, the code jumps to the put label, which calls put_device(hdev). If this drops the final reference, the device is freed. When the function then returns, the guard cleanup function runs and attempts to unlock the freed mutex. Use scoped_guard() instead of guard() to avoid the problem.

How severe is CVE-2026-98000?

Severity scoring for CVE-2026-98000 is pending analysis.

How do I fix CVE-2026-98000?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →