https://bugs.winehq.org/show_bug.cgi?id=51824
--- Comment #2 from Rémi Bernon rbernon@codeweavers.com --- Thanks! I sent an updated patch (https://source.winehq.org/patches/data/216077) that should fix that issue.
I initially didn't bother too much with checking which strategy should be used here, as I know that there's another location in winebus.sys where the last report may be overwritten.
It's much less likely to happen, as the reading thread is the one from hidclass.sys instead, which should only be busy reading, but it should probably be fixed as well at some point (more specifically it should probably queue the reports coming from the unix side instead of replacing the last report).