On Sat, Feb 18, 2012 at 23:55:34 +0100, Michael Karcher wrote:
libXi can cause heap corruption if it receices unknown device classes
in input devices, as it does not allocate any space to unknown classes,
yet it stores type and ID information of that class. If the unknown classes
are at the
I can't reproduce the bug with version 2:1.3-7
Reinhard
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4fa4420f.10...@gmx.net
On Sat, Feb 18, 2012 at 23:55:34 +0100, Michael Karcher wrote:
This behaviour is observable with current X servers in experimental. As
heap corruption is a security problem (malign X servers could try to exploit
client code using Xinput2), fixing this bug might be eligible for a stable
Package: libxi6
Version: 2:1.3-6
Severity: important
Tags: upstream patch
libXi can cause heap corruption if it receices unknown device classes
in input devices, as it does not allocate any space to unknown classes,
yet it stores type and ID information of that class. If the unknown classes
are
4 matches
Mail list logo