CVE-2026-98198

published 6 Oct 2026 · updated 1 Nov 2026

hwmon: (pwm-fan) Stop RPM timer before freeing tach data

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1e824fdb14a187ce56697e803b02b1e86243a755, Kernel 26d5ff79768548efb1e604bb6e8697c101e06269, Kernel 6f890d1fe8325ac8330473428b9a9d6526de1b32 and 4 more.

In the Linux kernel, the following vulnerability has been resolved: hwmon: (pwm-fan) Stop RPM timer before freeing tach data sample_timer() rearms the RPM timer and accesses the devm-managed ctx->tachs and ctx->pulses_per_revolution arrays. The cleanup action which stops the timer is registered before those arrays are allocated. Since devres releases entries in reverse order, driver detach can free the arrays before pwm_fan_cleanup() shuts down the timer. A timer expiry in that window accesses the freed tach data. With a KASAN kernel, a test-only kprobe delayed entry to pwm_fan_cleanup() while normal sysfs unbind ran. Each of three runs reported three four-byte reads and two four-byte writes in sample_timer() after its backing devm allocations had been freed. The helper did not invoke the timer callback, cleanup actions or free functions. With the fix, three matching unbind runs completed without KASAN, BUG, WARNING, Oops or panic. Instrumentation confirmed that timer retirement completed before the first timer backing allocation was released. Split timer retirement from the power cleanup and register its devres action after the timer backing data and IRQ actions are installed. This preserves the early power rollback action while ensuring the timer is retired before its backing data is released. Use timer_shutdown_sync() because the callback can rearm itself.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=5.12, >=01695410d4529e38fea6159fa9f1260c598290b0 <1e824fdb14a187ce56697e803b02b1e86243a755, >=01695410d4529e38fea6159fa9f1260c598290b0 <26d5ff79768548efb1e604bb6e8697c101e06269, >=01695410d4529e38fea6159fa9f1260c598290b0 <6f890d1fe8325ac8330473428b9a9d6526de1b32, >=01695410d4529e38fea6159fa9f1260c598290b0 <7743183d8b0f6ba88738805c824a255baae674b9, >=01695410d4529e38fea6159fa9f1260c598290b0 <a5ce3fe5335a24d0220958c6866830a6d5fa1cc0, >=01695410d4529e38fea6159fa9f1260c598290b0 <b48339b0a577783e4590a69e4cd2f2760ce33154, >=01695410d4529e38fea6159fa9f1260c598290b0 <d073d306e587c1f35aaf9c07c42e54a3d5895d8f1e824fdb14a187ce56697e803b02b1e86243a755, 26d5ff79768548efb1e604bb6e8697c101e06269, 6f890d1fe8325ac8330473428b9a9d6526de1b32, 7743183d8b0f6ba88738805c824a255baae674b9, a5ce3fe5335a24d0220958c6866830a6d5fa1cc0, b48339b0a577783e4590a69e4cd2f2760ce33154, d073d306e587c1f35aaf9c07c42e54a3d5895d8f

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-98198 severity on Zeptric[![CVE-2026-98198](https://zeptric.io/badge/cve/CVE-2026-98198.svg)](https://zeptric.io/cve/CVE-2026-98198)