# CVE-2024-9632: Xorg-x11-server: tigervnc: heap-based buffer overflow privilege escalation vulnerability > A heap-based buffer overflow in the X.org server allows local attackers to cause denial of service or escalate privileges via a crafted payload. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 30 Oct 2024 - **Updated:** 18 Mar 2026 - **Also known as:** ALSA-2024:10090, ALSA-2024:8798, ALSA-2024:9540, AZL-52026, AZL-52032, AZL-52035, BELL-CVE-2024-9632, DEBIAN-CVE-2024-9632, DLA-3940-1, DSA-5800-1, GHSA-cjcf-6ch6-g3rx, MGASA-2024-0357, OESA-2024-2352, RHSA-2024:10090, RHSA-2024:8798, RHSA-2024:9540, RHSA-2024:9579, RHSA-2024:9601, RHSA-2024:9690, RHSA-2024:9816, RHSA-2024:9818, RHSA-2024:9819, RHSA-2024:9820, RHSA-2024:9901, RLSA-2024:10090, RLSA-2024:8798, RLSA-2024:9540, SUSE-SU-2024:3786-1, SUSE-SU-2024:3787-1, SUSE-SU-2024:3788-1, SUSE-SU-2024:3789-1, SUSE-SU-2024:3790-1, SUSE-SU-2024:3791-1, SUSE-SU-2024:3866-1, SUSE-SU-2024:3867-1, UBUNTU-CVE-2024-9632, USN-7085-1, USN-7085-2, openSUSE-SU-2024:14466-1, openSUSE-SU-2024:14467-1 ## What is CVE-2024-9632? CVE-2024-9632 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 30 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description A flaw was found in the X.org server. Due to improperly tracked allocation size in _XkbSetCompatMap, a local attacker may be able to trigger a buffer overflow condition via a specially crafted payload, leading to denial of service or local privilege escalation in distributions where the X.org server is run with root privileges. Weakness: CWE-122 (Heap-based Buffer Overflow) ## Which versions are affected by CVE-2024-9632? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `tigervnc` | AlmaLinux:8 | All versions | 1.13.1-14.el8_10 | | `tigervnc-icons` | AlmaLinux:8 | All versions | 1.13.1-14.el8_10 | | `tigervnc-license` | AlmaLinux:8 | All versions | 1.13.1-14.el8_10 | | `tigervnc-selinux` | AlmaLinux:8 | All versions | 1.13.1-14.el8_10 | | `tigervnc-server` | AlmaLinux:8 | All versions | 1.13.1-14.el8_10 | | `tigervnc-server-minimal` | AlmaLinux:8 | All versions | 1.13.1-14.el8_10 | | `tigervnc-server-module` | AlmaLinux:8 | All versions | 1.13.1-14.el8_10 | | `xorg-x11-server-Xdmx` | AlmaLinux:8 | All versions | 1.20.11-25.el8_10 | | `xorg-x11-server-Xephyr` | AlmaLinux:8 | All versions | 1.20.11-25.el8_10 | | `xorg-x11-server-Xnest` | AlmaLinux:8 | All versions | 1.20.11-25.el8_10 | | `xorg-x11-server-Xorg` | AlmaLinux:8 | All versions | 1.20.11-25.el8_10 | | `xorg-x11-server-Xvfb` | AlmaLinux:8 | All versions | 1.20.11-25.el8_10 | | `xorg-x11-server-Xwayland` | AlmaLinux:8 | All versions | 21.1.3-17.el8_10 | | `xorg-x11-server-common` | AlmaLinux:8 | All versions | 1.20.11-25.el8_10 | | `xorg-x11-server-devel` | AlmaLinux:8 | All versions | 1.20.11-25.el8_10 | | `xorg-x11-server-source` | AlmaLinux:8 | All versions | 1.20.11-25.el8_10 | | `tigervnc` | AlmaLinux:9 | All versions | 1.14.1-1.el9_5 | | `tigervnc-icons` | AlmaLinux:9 | All versions | 1.14.1-1.el9_5 | | `tigervnc-license` | AlmaLinux:9 | All versions | 1.14.1-1.el9_5 | | `tigervnc-selinux` | AlmaLinux:9 | All versions | 1.14.1-1.el9_5 | | `tigervnc-server` | AlmaLinux:9 | All versions | 1.14.1-1.el9_5 | | `tigervnc-server-minimal` | AlmaLinux:9 | All versions | 1.14.1-1.el9_5 | | `tigervnc-server-module` | AlmaLinux:9 | All versions | 1.14.1-1.el9_5 | | `tigervnc` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.13.1-14.el8_10 | | `tigervnc-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.13.1-14.el8_10 | | `tigervnc-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.13.1-14.el8_10 | | `tigervnc-icons` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.13.1-14.el8_10 | | `tigervnc-license` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.13.1-14.el8_10 | | `tigervnc-selinux` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.13.1-14.el8_10 | | `tigervnc-server` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.13.1-14.el8_10 | | `tigervnc-server-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.13.1-14.el8_10 | | `tigervnc-server-minimal` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.13.1-14.el8_10 | | `tigervnc-server-minimal-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.13.1-14.el8_10 | | `tigervnc-server-module` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.13.1-14.el8_10 | | `tigervnc-server-module-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.13.1-14.el8_10 | | `xorg-x11-server` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.20.11-25.el8_10 | | `xorg-x11-server-Xdmx` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.20.11-25.el8_10 | | `xorg-x11-server-Xdmx-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.20.11-25.el8_10 | | `xorg-x11-server-Xephyr` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.20.11-25.el8_10 | | `xorg-x11-server-Xephyr-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.20.11-25.el8_10 | ## How do I fix CVE-2024-9632? Apply the vendor's patch. ## Is CVE-2024-9632 being exploited? There is no known exploitation of CVE-2024-9632 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-9632 and fix it if it is affected. What it is: CVE-2024-9632 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 30 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-9632 in the wild and no public exploit code. Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-9632/ (Markdown: https://insights.sbomify.com/CVE-2024-9632/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-9632 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-9632 - OSV: https://osv.dev/vulnerability/CVE-2024-9632 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-9632/ Summaries are generated and may contain mistakes; the official description above is the record.