fs_read_glyphs() in the libXfont2 font-server client (src/fc/fserve.c) indexes the per-character encoding[] array using num_chars from the FS_QueryXBitmaps16 reply, but that array was allocated with a size derived from num_extents in the separate FS_QueryXExtents16 reply. The two CARD32 fields are never cross-checked. A malicious or compromised font server can send a small num_extents (e.g. 1) in the extents reply, then a large num_chars (e.g. 100000) in the bitmaps reply. This causes attacker-controlled out-of-bounds heap read and writes.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alma_linux | — | Upgrade libXfont2Upgrade libXfont2-devel | Oct 11, 2026 | Aug 17, 2026 |
| Amazon Linux Ami 2 | — | Upgrade libXfont-develUpgrade libXfontUpgrade libXfont2-debuginfoUpgrade libXfont-debuginfoUpgrade libXfont2Upgrade libXfont2-devel | Oct 19, 2026 | Oct 19, 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 libXfont2-develUpgrade libXfont2Upgrade 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