X.Org font libraries fix heap bugs reachable from the X server
A crafted encoding file can write past a heap buffer and, where the server runs as root, may allow local privilege escalation; a separate PCF parser bug can read invalid memory.
X.Org has fixed two font-parsing flaws in libraries the X server uses to load fonts, one of which can become a local privilege escalation when the server runs as root.
CVE-2026-109908 is a heap out-of-bounds write in libfontenc, the library that parses font encoding files. The parser takes a size value from the encoding file and uses it to compute where to write, without checking that the index stays inside a fixed 65,536-entry buffer. A crafted encoding file writes past that allocation. The Xorg and Xwayland servers pull libfontenc in through libXfont2 and parse encoding files in the server process while rasterizing fonts. A local user who can place a font file and an encoding file on a path the server reads can trigger the write. Where that server runs as root, X.Org says the result is potential local privilege escalation. Adam Bedard, working with TrendAI's Zero Day Initiative, reported the flaw. It is fixed in libfontenc 1.1.10.
CVE-2026-109909 is an out-of-bounds heap read in libXfont's PCF font parser. A skip routine accepts a signed count and does not reject negative values. A crafted PCF file can force that count negative, so the parser walks its buffer pointer backward past the start of the buffer and then reads through the corrupted pointer, from invalid heap memory or unmapped pages. Anyone who can make the X server, or another application linked to libXfont, load that font can trigger the read, which X.Org says may leak memory. The fix is in libXfont2 2.0.10.
Both bugs are reached by font files the server is willing to open, not by a remote network protocol. Sites that still run the X server as root, or that let untrusted users add fonts on server font paths, are the ones with a privilege boundary at stake.