Live › vulnerability › CVE-2026-98645
Go to dashboardThe WinWing HID driver in the Linux kernel passes devres-managed memory to the force-feedback core, which frees it with kfree() on device teardown. The same allocation is then freed again by devres, causing a use-after-free and double free that can corrupt kernel memory.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel with the winwing HID driver, typically hosts with WinWing flight or sim input devices attached. The bug triggers on driver unbind, module removal, hot-unplug or system suspend, so machines without WinWing hardware or with the driver not loaded can skip it.
No product ranges from the sources yet.
lsmod | grep winwinguname -r and compare against the fixed release in the NVD entry unknownEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-98645")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.