https://bugs.winehq.org/show_bug.cgi?id=46472
--- Comment #3 from tjb troyb@us.ibm.com --- (In reply to Fabian Maurer from comment #1)
AFAIK the linux kernel shouldn't break userland programs. Reverting the kernel commit fixed the issue? If so, did you already ask on the linux mailinglist?
According to the commit, which I attached, this "corrected" behavior in PTRACE_POKUSER hardware breakpoint functions. I have no idea what this function is or what the "correct" behavior is supposed to be, so I would not even know what to ask on the kernel mailing list, all I can say is the change causes a program to bomb on wine which used to work. It needs to be addressed by an expert, i.e. a wine dev who used these commands and understands that this kernel patch is either broke, or the wine code is relying on unspecified behavior and needs to be updated.