CVE-2026-98198
Last modified
CVE-2026-98198 is a vulnerability of currently unknown severity. 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.
Description
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 Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 01695410d4529e38fea6159fa9f1260c598290b0, < 1e824fdb14a187ce56697e803b02b1e86243a755; >= 01695410d4529e38fea6159fa9f1260c598290b0, < a5ce3fe5335a24d0220958c6866830a6d5fa1cc0; >= 01695410d4529e38fea6159fa9f1260c598290b0, < b48339b0a577783e4590a69e4cd2f2760ce33154; >= 01695410d4529e38fea6159fa9f1260c598290b0, < 26d5ff79768548efb1e604bb6e8697c101e06269 |
| Linux | Linux | 5.12 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-98198?
How severe is CVE-2026-98198?
How do I fix CVE-2026-98198?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-98192In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98193In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98194In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98195In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98196In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98197In the Linux kernel, the following vulnerability has been re…7
- CVE-2026-98199In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9820Mattermost versions 11.7.x <= 11.7.2, 10.11.x <= 10.11.19 fa…3.8
- CVE-2026-98200In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98201In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98202In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98203In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-98198?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
