Skip to main content
VulnerabilityPublished Updated

CVE-2024-31080: xorg-server · Buffer Over-read

Affects xorg-serverSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.3 High.

Data as of 21 Nov 2026, 17:34 UTC

CVSS 3.1 base score
7.3High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.17.3
EPSS
0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Apr 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
xorg-serverAffected
  • >=29.1.0
Fixed in–

AI-suggested

To mitigate CVE-2024-31080, organizations should prioritize updating the X.org server to a patched version once available from trusted vendors or distributions. In the absence of an official patch, consider applying vendor-provided workarounds or configuration changes that disable or restrict the use of the ProcXIGetSelectedEvents() function or limit connections from clients with differing endianness. Restrict local user access to systems running the vulnerable X.org server to trusted personnel only, minimizing the risk of exploitation by unprivileged users. Employ strict access controls and monitoring to detect unusual local client connections or crashes of the X server process. Use memory protection mechanisms such as Address Space Layout Randomization (ASLR) and heap protection features to reduce the impact of memory corruption vulnerabilities. Additionally, consider isolating critical graphical systems in secure environments or containers to limit the blast radius of potential crashes or data leaks. Regularly audit and monitor logs for segmentation faults or abnormal X server behavior that could indicate exploitation attempts. Finally, educate system administrators and users about the risks associated with local privilege misuse and enforce least privilege principles.

Description

A heap-based buffer over-read vulnerability was found in the X.org server's ProcXIGetSelectedEvents() function. This issue occurs when byte-swapped length values are used in replies, potentially leading to memory leakage and segmentation faults, particularly when triggered by a client with a different endianness. This vulnerability could be exploited by an attacker to cause the X server to read heap memory values and then transmit them back to the client until encountering an unmapped page, resulting in a crash. Despite the attacker's inability to control the specific memory copied into the replies, the small length values typically stored in a 32-bit integer can result in significant attempted out-of-bounds reads.

References

Community reviews

Loading reviews…