fs_read_glyphs() in the libXfont2 font-server client (src/fc/fserve.c) copies each glyph's bitmap into a single buffer. Existing checks validates only that the source slice (position, length) lies within the source bitmap buffer. It does not check whether the running destination cursor has exceeded the allocation.
A malicious font server can send overlapping source offsets -- for example 1000 glyphs each referencing {position:0, length:64} with nbytes=64. Each individual source range passes the existing validation, but the cumulative writes total 64000 bytes into a 64-byte destination buffer. This is a heap buffer overflow with attacker-controlled content.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alma_linux | — | Upgrade libXfont2-develUpgrade libXfont2 | Oct 11, 2026 | Aug 17, 2026 |
| Freebsd | — | Upgrade libXfont2 | Aug 10, 2026 | Aug 7, 2026 |
| Redhat_linux | — | Upgrade libXfont2-debugsourceUpgrade libXfont2Upgrade libXfont2-debuginfoUpgrade libXfont2-devel | Aug 10, 2026 | Aug 5, 2026 |
| Rocky_linux | — | Upgrade libXfont2Upgrade libXfont2-develUpgrade libXfont2-debugsourceUpgrade libXfont2-debuginfo | Aug 20, 2026 | Aug 17, 2026 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub