libinput vulnerabilities

In libinput before 1.30.4 and 1.31.x before 1.31.3, libinput-device-group unescaped phys output can inject udev properties leading to arbitrary root code execution.

A dangling pointer flaw was found in libinput. It occurs when a garbage collection cleanup function is called, leaving a pointer that can then be printed to system logs. This could potentially expose sensitive data if the memory location is re-used. Exploitation requires Lua plugins to be enabled in libinput and loaded by the compositor, and the ability to deploy a plugin file in specific system directories.

A flaw was found in libinput that allows a local attacker to bypass security restrictions by placing a specially crafted Lua bytecode file in certain system or user configuration directories. The attacker can run unauthorized code with the same permissions as the program using libinput, such as a graphical compositor. This could lead to monitoring keyboard input and sending that information to an external location.