First published: Thu Nov 11 2010(Updated: )
Given the right combination of ThinkPad and X.org, just reading the video output control state is enough to hard-crash X.org. Until the day I somehow find out a model or BIOS cut date to not provide this feature to ThinkPads that can do video switching through X RandR, change permissions so that only processes with CAP_SYS_ADMIN can access any sort of video output control state. This bug could be considered a local DoS I suppose, as it allows any non-privledged local user to cause some versions of X.org to hard-crash some ThinkPads. Reported-by: Jidanni <jidanni> Signed-off-by: Henrique de Moraes Holschuh <hmh.br> Cc: stable Upstream commit: <a href="http://git.kernel.org/linus/b525c06cdbd8a3963f0173ccd23f9147d4c384b5">http://git.kernel.org/linus/b525c06cdbd8a3963f0173ccd23f9147d4c384b5</a>
Affected Software | Affected Version | How to fix |
---|---|---|
X.Org |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-652122 is critical as it can lead to a complete crash of the X.org server.
To fix REDHAT-BUG-652122, change the permissions related to the video output control state on affected ThinkPad systems.
REDHAT-BUG-652122 affects certain ThinkPad models that use X.org for video switching through X RandR.
A potential workaround for REDHAT-BUG-652122 is to avoid using the video output control states that trigger the crash.
Consequences of REDHAT-BUG-652122 include data loss and system stability issues due to the X.org server crash.