{"id":"USN-6587-4","aliases":[],"status":"published","title":"xorg-server, xwayland regression","description":"USN-6587-1 fixed vulnerabilities in X.Org X Server. The fix was incomplete\nresulting in a possible regression. This update fixes the problem.\n\nOriginal advisory details:\n\n Jan-Niklas Sohn discovered that the X.Org X Server incorrectly handled\n memory when processing the DeviceFocusEvent and ProcXIQueryPointer APIs. An\n attacker could possibly use this issue to cause the X Server to crash,\n obtain sensitive information, or execute arbitrary code. (CVE-2023-6816)\n\n Jan-Niklas Sohn discovered that the X.Org X Server incorrectly handled\n reattaching to a different master device. An attacker could use this issue\n to cause the X Server to crash, leading to a denial of service, or possibly\n execute arbitrary code. (CVE-2024-0229)\n\n Olivier Fourdan and Donn Seeley discovered that the X.Org X Server\n incorrectly labeled GLX PBuffers when used with SELinux. An attacker could\n use this issue to cause the X Server to crash, leading to a denial of\n service. (CVE-2024-0408)\n\n Olivier Fourdan discovered that the X.Org X Server incorrectly handled\n the curser code when used with SELinux. An attacker could use this issue to\n cause the X Server to crash, leading to a denial of service.\n (CVE-2024-0409)\n\n Jan-Niklas Sohn discovered that the X.Org X Server incorrectly handled\n memory when processing the XISendDeviceHierarchyEvent API. An attacker\n could possibly use this issue to cause the X Server to crash, or execute\n arbitrary code. (CVE-2024-21885)\n\n Jan-Niklas Sohn discovered that the X.Org X Server incorrectly handled\n devices being disabled. An attacker could possibly use this issue to cause\n the X Server to crash, or execute arbitrary code. (CVE-2024-21886)","facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"published":"2024-02-01T13:22:21Z","modified":"2026-06-25T13:31:40Z","fixes":[{"ecosystem":"Ubuntu:Pro:16.04:LTS","package":"xorg-server","fixed_in":["2:1.18.4-0ubuntu0.12+esm10"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:18.04:LTS","package":"xorg-server","fixed_in":["2:1.19.6-1ubuntu4.15+esm5"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"xorg-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.18.4-0ubuntu0.12+esm10"}]}],"versions":["2:1.17.2-1ubuntu9","2:1.17.2-1ubuntu10","2:1.17.3-2ubuntu1","2:1.17.3-2ubuntu2","2:1.17.3-2ubuntu3","2:1.17.3-2ubuntu4","2:1.18.1-1ubuntu3","2:1.18.1-1ubuntu4","2:1.18.3-1ubuntu1","2:1.18.3-1ubuntu2","2:1.18.3-1ubuntu2.2","2:1.18.3-1ubuntu2.3","2:1.18.4-0ubuntu0.1","2:1.18.4-0ubuntu0.2","2:1.18.4-0ubuntu0.3","2:1.18.4-0ubuntu0.4","2:1.18.4-0ubuntu0.6","2:1.18.4-0ubuntu0.7","2:1.18.4-0ubuntu0.8","2:1.18.4-0ubuntu0.9","2:1.18.4-0ubuntu0.10","2:1.18.4-0ubuntu0.11","2:1.18.4-0ubuntu0.12","2:1.18.4-0ubuntu0.12+esm1","2:1.18.4-0ubuntu0.12+esm2","2:1.18.4-0ubuntu0.12+esm4","2:1.18.4-0ubuntu0.12+esm5","2:1.18.4-0ubuntu0.12+esm6","2:1.18.4-0ubuntu0.12+esm8","2:1.18.4-0ubuntu0.12+esm9"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"xorg-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.19.6-1ubuntu4.15+esm5"}]}],"versions":["2:1.19.5-0ubuntu2","2:1.19.6-1ubuntu1","2:1.19.6-1ubuntu2","2:1.19.6-1ubuntu3","2:1.19.6-1ubuntu4","2:1.19.6-1ubuntu4.1","2:1.19.6-1ubuntu4.2","2:1.19.6-1ubuntu4.3","2:1.19.6-1ubuntu4.4","2:1.19.6-1ubuntu4.5","2:1.19.6-1ubuntu4.6","2:1.19.6-1ubuntu4.7","2:1.19.6-1ubuntu4.8","2:1.19.6-1ubuntu4.9","2:1.19.6-1ubuntu4.10","2:1.19.6-1ubuntu4.11","2:1.19.6-1ubuntu4.12","2:1.19.6-1ubuntu4.13","2:1.19.6-1ubuntu4.14","2:1.19.6-1ubuntu4.15","2:1.19.6-1ubuntu4.15+esm1","2:1.19.6-1ubuntu4.15+esm3","2:1.19.6-1ubuntu4.15+esm4"]}],"references":[{"url":"https://ubuntu.com/security/notices/USN-6587-4","tags":["advisory"]},{"url":"https://launchpad.net/bugs/2051536","tags":["report"]}],"sources":{"osv":[{"id":"USN-6587-4","title":"xorg-server, xwayland regression","description":"USN-6587-1 fixed vulnerabilities in X.Org X Server. The fix was incomplete\nresulting in a possible regression. This update fixes the problem.\n\nOriginal advisory details:\n\n Jan-Niklas Sohn discovered that the X.Org X Server incorrectly handled\n memory when processing the DeviceFocusEvent and ProcXIQueryPointer APIs. An\n attacker could possibly use this issue to cause the X Server to crash,\n obtain sensitive information, or execute arbitrary code. (CVE-2023-6816)\n\n Jan-Niklas Sohn discovered that the X.Org X Server incorrectly handled\n reattaching to a different master device. An attacker could use this issue\n to cause the X Server to crash, leading to a denial of service, or possibly\n execute arbitrary code. (CVE-2024-0229)\n\n Olivier Fourdan and Donn Seeley discovered that the X.Org X Server\n incorrectly labeled GLX PBuffers when used with SELinux. An attacker could\n use this issue to cause the X Server to crash, leading to a denial of\n service. (CVE-2024-0408)\n\n Olivier Fourdan discovered that the X.Org X Server incorrectly handled\n the curser code when used with SELinux. An attacker could use this issue to\n cause the X Server to crash, leading to a denial of service.\n (CVE-2024-0409)\n\n Jan-Niklas Sohn discovered that the X.Org X Server incorrectly handled\n memory when processing the XISendDeviceHierarchyEvent API. An attacker\n could possibly use this issue to cause the X Server to crash, or execute\n arbitrary code. (CVE-2024-21885)\n\n Jan-Niklas Sohn discovered that the X.Org X Server incorrectly handled\n devices being disabled. An attacker could possibly use this issue to cause\n the X Server to crash, or execute arbitrary code. (CVE-2024-21886)\n","status":"published","published":"2024-02-01T13:22:21Z","modified":"2026-06-25T13:31:40.397849851Z","updated_at":"2026-11-02T16:58:17.305935Z"}]}}