CVE-2026-98645
Last modified
CVE-2026-98645 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: HID: winwing: fix use-after-free in force feedback teardown winwing_init_ff() passes the driver's private data, allocated with devm_kzalloc() in winwing_probe(), as the effect context to input_ff_create_memless(). The memoryless force-feedback core takes ownership of that pointer and frees it with kfree() from input_ff_destroy() (ml_ff_destroy()) when the input device is destroyed. Freeing a devm-managed allocation with kfree() is an invalid free, and the same object is then released again by devres when the HID device is torn down, a double free.
Description
In the Linux kernel, the following vulnerability has been resolved: HID: winwing: fix use-after-free in force feedback teardown winwing_init_ff() passes the driver's private data, allocated with devm_kzalloc() in winwing_probe(), as the effect context to input_ff_create_memless(). The memoryless force-feedback core takes ownership of that pointer and frees it with kfree() from input_ff_destroy() (ml_ff_destroy()) when the input device is destroyed. Freeing a devm-managed allocation with kfree() is an invalid free, and the same object is then released again by devres when the HID device is torn down, a double free. As the allocation also embeds the LED class devices, their timers and work item live on freed memory and the slab gets corrupted. This triggers on unbind, rmmod, hot-unplug and on system suspend, where the firmware cache walks the now-corrupt devres list. KASAN reports: BUG: KASAN: invalid-free in input_ff_destroy Allocated by task N: winwing_probe Pass NULL as the memless context instead and fetch the driver data from the input device in winwing_play_effect(): the HID core already stores the hid_device as the input device's drvdata. The force-feedback core then owns nothing that it must not free.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 42d020b54edc57d03749bed75976f1e962a9fbfa, < 2b25f11ec52ea0a82334d5b83ee321f6b0a35923; >= 42d020b54edc57d03749bed75976f1e962a9fbfa, < a1a5ad37e50ceb192c07ac7e2d7143638cd4d110 |
| Linux | Linux | 7.1 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-98645?
How severe is CVE-2026-98645?
How do I fix CVE-2026-98645?
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-9864Fortra BoKS Server Agent contains a predictable password gen…4.8
- CVE-2026-98640In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98641In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98642In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98643In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98644In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98646In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98647In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98648In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98649In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98650In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98651In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-98645?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
