Поиск уязвимостей
Количество 22
Количество 22
openSUSE-SU-2026:21539-1
Security update for libXfont2
SUSE-SU-2026:3500-1
Security update for libXfont2
SUSE-SU-2026:3499-1
Security update for libXfont2
RLSA-2026:55448
Important: libXfont2 security update
RLSA-2026:55447
Important: libXfont2 security update
RLSA-2026:55446
Important: libXfont2 security update
ELSA-2026-62231-0
ELSA-2026-62231-0: libXfont2 security update (IMPORTANT)
ELSA-2026-55448
ELSA-2026-55448: libXfont2 security update (IMPORTANT)
ELSA-2026-55447
ELSA-2026-55447: libXfont2 security update (IMPORTANT)
ELSA-2026-55446
ELSA-2026-55446: libXfont2 security update (IMPORTANT)
CVE-2026-59679
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.
CVE-2026-59679
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.
CVE-2026-59679
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.
CVE-2026-59679
fs_read_glyphs() heap OOB read/write via encoding array index mismatch in libXfont2
CVE-2026-59679
fs_read_glyphs() in the libXfont2 font-server client (src/fc/fserve.c) ...
CVE-2026-44950
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.
CVE-2026-44950
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.
CVE-2026-44950
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.
CVE-2026-44950
fs_read_glyphs() heap buffer overflow via cumulative glyph data overflow in libXfont2
CVE-2026-44950
fs_read_glyphs() in the libXfont2 font-server client (src/fc/fserve.c) ...
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
openSUSE-SU-2026:21539-1 Security update for libXfont2 | 3 месяца назад | |||
SUSE-SU-2026:3500-1 Security update for libXfont2 | 4 месяца назад | |||
SUSE-SU-2026:3499-1 Security update for libXfont2 | 4 месяца назад | |||
RLSA-2026:55448 Important: libXfont2 security update | 3 месяца назад | |||
RLSA-2026:55447 Important: libXfont2 security update | 3 месяца назад | |||
RLSA-2026:55446 Important: libXfont2 security update | 3 месяца назад | |||
ELSA-2026-62231-0 ELSA-2026-62231-0: libXfont2 security update (IMPORTANT) | около 2 месяцев назад | |||
ELSA-2026-55448 ELSA-2026-55448: libXfont2 security update (IMPORTANT) | 3 месяца назад | |||
ELSA-2026-55447 ELSA-2026-55447: libXfont2 security update (IMPORTANT) | 3 месяца назад | |||
ELSA-2026-55446 ELSA-2026-55446: libXfont2 security update (IMPORTANT) | 3 месяца назад | |||
CVE-2026-59679 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. | CVSS3: 9 | 0% Низкий | 2 месяца назад | |
CVE-2026-59679 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. | CVSS3: 7.5 | 0% Низкий | 4 месяца назад | |
CVE-2026-59679 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. | CVSS3: 9 | 0% Низкий | 2 месяца назад | |
CVE-2026-59679 fs_read_glyphs() heap OOB read/write via encoding array index mismatch in libXfont2 | 0% Низкий | 2 месяца назад | ||
CVE-2026-59679 fs_read_glyphs() in the libXfont2 font-server client (src/fc/fserve.c) ... | CVSS3: 9 | 0% Низкий | 2 месяца назад | |
CVE-2026-44950 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. | CVSS3: 9 | 0% Низкий | 2 месяца назад | |
CVE-2026-44950 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. | CVSS3: 7.5 | 0% Низкий | 4 месяца назад | |
CVE-2026-44950 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. | CVSS3: 9 | 0% Низкий | 2 месяца назад | |
CVE-2026-44950 fs_read_glyphs() heap buffer overflow via cumulative glyph data overflow in libXfont2 | 0% Низкий | 2 месяца назад | ||
CVE-2026-44950 fs_read_glyphs() in the libXfont2 font-server client (src/fc/fserve.c) ... | CVSS3: 9 | 0% Низкий | 2 месяца назад |
Уязвимостей на страницу