High [CVE-2026-56002] PCF Font Parsing Heap Buffer Overflow
This high-severity Red Hat Linux advisory covers CVE-2026-56002 affecting Red Hat Enterprise Linux 10.0 Extended Update Support, Red Hat Enterprise Linux 7 Extended Lifecycle Support, Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
A heap bufferflow in pcfReadFont() due to missing glyph bounds checking in libXfont2 before 2.0.8 allows attackers authenticated as X client to execute code within the X server. A flaw was found in libXfont2.
A specially crafted PCF (Portable Compiled Format) font file, when processed by libXfont2, can lead to a buffer overflow. This occurs because the font parsing process does not properly validate the size of a bitmap buffer against the glyph metrics provided in the malicious font file.
An attacker could exploit this vulnerability by providing a malicious font, potentially leading to arbitrary code execution or a denial of service. This is an Important flaw in libXfont2, affecting Red Hat Enterprise Linux.
A heap buffer overflow during PCF font file parsing can lead to arbitrary code execution or denial of service. Exploitation requires processing a specially crafted font file, but does not necessitate rendering.
Red Hat severity: Important — CVSS 7.3 (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H). Weakness: CWE-787.
Affected products named by the advisory: Red Hat Enterprise Linux 10.0 Extended Update Support; Red Hat Enterprise Linux 7 Extended Lifecycle Support; Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support; Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On; and 8 more.
- < 2.0.8
Official advisory · high-confidence parse· fetched 9 days ago·verify at source
- libXfont2-0:2.0.6-5.el10_2.1
- libXfont2-0:2.0.6-5.el10_0.1
- libXfont2-0:2.0.3-2.el7_9
- libXfont2-0:2.0.3-2.el8_10.1
- libXfont2-0:2.0.3-2.el8_4.1
- libXfont2-0:2.0.3-2.el8_6.1
- libXfont2-0:2.0.3-2.el8_8.1
- libXfont2-0:2.0.3-12.el9_8.1
- libXfont2-0:2.0.3-12.el9_2.1
- libXfont2-0:2.0.3-12.el9_4.1
- libXfont2-0:2.0.3-12.el9_6.1
- RHSA-2026:47079
- RHSA-2026:51061
- RHSA-2026:51063
- RHSA-2026:47103
- RHSA-2026:51060
- RHSA-2026:51066
- RHSA-2026:51067
- RHSA-2026:47084
- RHSA-2026:51062
- RHSA-2026:51058
- RHSA-2026:51059
Official advisory · high-confidence parse· fetched 9 days ago·verify at source
Mitigation
Upgrade to a fixed release: libXfont2-0:2.0.6-5.el10_2.1, libXfont2-0:2.0.6-5.el10_0.1, libXfont2-0:2.0.3-2.el7_9, libXfont2-0:2.0.3-2.el8_10.1, libXfont2-0:2.0.3-2.el8_4.1, libXfont2-0:2.0.3-2.el8_6.1. That is the remediation for this advisory.
The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.
Official advisory · high-confidence parse· fetched 9 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.