On this page (7 sections)
Ubuntu published USN-9124-1 on 17 November 2026, fixing three vulnerabilities in RenderDoc, a stand-alone graphics debugging tool. Two are integer overflows that can lead to a buffer overflow, and the third is a symbolic link flaw that could let a local user escalate privileges.
RenderDoc is not a typical web server package, so most website operators will not have it installed. The notice matters mainly to developers, agencies and build or test hosts running Ubuntu 20.04 LTS or 22.04 LTS where the tool has been installed. For those releases, Ubuntu lists the fixes as available through Ubuntu Pro.
What was fixed
The Ubuntu notice covers three issues, all first published in the National Vulnerability Database on 7 June 2023. Ubuntu's own advisory describes them as follows.
| CVE | Weakness | CVSS | Impact per Ubuntu |
|---|---|---|---|
| CVE-2023-33863 | CWE-190, integer overflow | 9.8 Critical | Array sizes not verified when serialising strings; possible buffer overflow, denial of service or code execution |
| CVE-2023-33864 | CWE-190, integer overflow | 9.8 Critical | Certain socket reads mishandled; a remote attacker could possibly cause a heap buffer overflow, leading to denial of service or code execution |
| CVE-2023-33865 | CWE-59, improper link resolution | 7.8 High | Symbolic links followed when opening the log file in /tmp/RenderDoc; a local attacker could possibly escalate privileges |
Technical details in plain terms
An integer overflow happens when a calculation produces a number too large for the space reserved for it, so it wraps around to something small or negative. If the program then uses that value to size a memory buffer, it can write past the end of the buffer.
Per the CVE text summarized in the GitHub advisory for CVE-2023-33863, the flaw is in SerialiseValue: 0xffffffff is sign-extended to 0xffffffffffffffff (SIZE_MAX), and the code then attempts to add 1. For CVE-2023-33864, the CVE record says StreamReader::ReadFromExternal uses uint32_t(m_BufferSize-m_InputSize) even though m_InputSize can exceed m_BufferSize. The research does not include the GitHub advisory for CVE-2023-33864 beyond a short summary, so Ubuntu's description (certain socket reads handled incorrectly) is the best plain-language reference.
The third flaw is a link-following problem (CWE-59). According to the CVE record, RenderDoc relies on the /tmp/RenderDoc directory regardless of ownership. Ubuntu says RenderDoc followed symbolic links when opening its log file in that directory, and that a local attacker could possibly use this to escalate privileges. The GitHub advisory for CVE-2023-33865 scores it as local attack vector, low complexity, low privileges required and no user interaction.
Who is realistically exposed
- Developer workstations and shared build or GPU test machines on Ubuntu 20.04 or 22.04 with RenderDoc packages installed.
- Multi-user systems, where the /tmp/RenderDoc symlink issue is most relevant because it requires a local attacker.
- Typical production web servers are unlikely to be affected unless someone installed the tool there.
A version note: the CVE records say RenderDoc before 1.27, while the GitHub advisory text says through 1.26. The two wordings appear consistent, but the research does not confirm the exact boundary. Ubuntu lists fixed package versions (1.18+dfsg-1ubuntu0.1~esm1 and 1.6+dfsg-1ubuntu0.1~esm1) without describing how they were built, so compare your installed package versions against the notice rather than against the upstream 1.27 number.
How to check your systems
This read-only command lists any installed RenderDoc packages and their versions on Ubuntu. If it prints nothing, the packages are not installed.
dpkg -l | grep -i renderdocCompare the version column with the fixed versions below. A version ending in ubuntu0.1~esm1 matches the fixed version listed in the notice.
| Release | Packages | Fixed version |
|---|---|---|
| Ubuntu 22.04 LTS (jammy) | librenderdoc, python3-renderdoc, qrenderdoc, renderdoccmd | 1.18+dfsg-1ubuntu0.1~esm1 |
| Ubuntu 20.04 LTS (focal) | renderdoc | 1.6+dfsg-1ubuntu0.1~esm1 |
To see whether the machine has Ubuntu Pro attached, which the notice lists as the way to receive these fixes, run the status command below. It prints whether services such as ESM Apps are enabled.
pro statusWhat to do now
Ubuntu states that the fixes are available with Ubuntu Pro via ESM Apps, and that a community fix might become publicly available in the future. Ubuntu Pro is free for up to five machines, per the notice.
- Find every Ubuntu 20.04 and 22.04 machine with RenderDoc installed, including developer laptops and build hosts.
- Remove RenderDoc from any server that does not need it. The least exposed package is the one that is not installed.
- Attach Ubuntu Pro and enable ESM Apps on machines that need the tool, then apply updates.
- Verify the installed version matches the fixed version in the table above.
- On shared machines, check that /tmp/RenderDoc is owned by the expected user and contains no unexpected symbolic links.
- Restart any running RenderDoc processes after updating so the old code is no longer in use.
Ubuntu's notice says a standard system update makes the necessary changes once the machine can receive the ESM Apps packages. The commands differ by release because the package names differ. On Ubuntu 22.04, run the following with sudo. It refreshes package lists and upgrades only the four RenderDoc packages. Afterwards, rerun the dpkg check to confirm the 1.18+dfsg-1ubuntu0.1~esm1 version.
sudo apt update
sudo apt install --only-upgrade librenderdoc python3-renderdoc qrenderdoc renderdoccmdOn Ubuntu 20.04 the notice lists a single package named renderdoc. This command refreshes package lists and upgrades it, after which the installed version should be 1.6+dfsg-1ubuntu0.1~esm1. The 22.04 package list in the notice does not include a package named renderdoc, so do not use this command there.
sudo apt update
sudo apt install --only-upgrade renderdocDetection and monitoring afterwards
The research gives no indicators of compromise for these flaws, so verification comes down to inventory and hygiene. Re-run the dpkg check after patching and keep a list of hosts that carry developer tooling, since these are often missed by server patch routines.
- Review /tmp/RenderDoc on shared machines for unexpected symbolic links or ownership by another user.
- Include developer and build hosts in your regular package version audits, not only production servers.
If you also run public websites on Ubuntu, the Webforta security scanner can check the externally visible side of those sites, but it does not see developer tools installed on a host. For wider hardening of Linux-hosted sites, see the small business website security guide.
Exploitation status and context
None of the three CVEs carries a CISA KEV entry in the research, and no source here reports exploitation in the wild. Public technical write-ups do exist: the CVE references include a Qualys advisory, a Full Disclosure post and a Packet Storm entry, each tagged as containing exploit information. The GitHub advisory pages list EPSS scores of 4.192% for CVE-2023-33863 and CVE-2023-33864 and 0.898% for CVE-2023-33865, which are probability estimates, not evidence of attacks.
The flaws were published in June 2023, and other distributions have also published notices, including a Debian LTS announcement and a Gentoo advisory.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
