CVE-2026-98645

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.