CVE-2024-0408: Xorg-x11-server: selinux unlabeled glx pbuffer
A flaw was found in the X.Org server. The GLX PBuffer code does not call the XACE hook when creating the buffer, leaving it unlabeled. When the client issues another request to access that resource (as with a GetGeometry) or when it creates another resource that needs to access that buffer, such as a GC, the XSELINUX code will try to use an object that was never labeled and crash because the SID is NULL.
Other sources
The XSELINUX code in the Xserver labels the X resources based on a hook. What happens here is that the GLX PBuffer code does not call that XACE hook when creating the buffer, so it remains unlabeled, and when the client issues another request to access that resource (as here with a GetGeometry) or even when it creates another resource which needs to access that buffer (such as a GC), the XSELINUX code will try to use an object that was never labeled and crash because the SID is NULL.
— Red Hat
Xorg-x11-server: selinux unlabeled glx pbuffer
— Microsoft
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-0408?
CVE-2024-0408 is considered to have a moderate severity due to potential access control issues.
How do I fix CVE-2024-0408?
To fix CVE-2024-0408, upgrade the affected packages to versions 21.1.11 of xorg-server or 23.2.4 of xwayland.
Which software packages are affected by CVE-2024-0408?
CVE-2024-0408 affects packages such as xorg-server, xwayland, and TigerVNC across various versions.
What might an attacker achieve by exploiting CVE-2024-0408?
An attacker exploiting CVE-2024-0408 could potentially gain unauthorized access to certain resources.
Is there a workaround for CVE-2024-0408 until I can apply a patch?
Currently, there are no specific workarounds available for CVE-2024-0408; patching is strongly recommended.