ALPINE-CVE-2026-93522: Buffer Overflow

Q: Who can exploit this issue?

An authenticated X client can trigger the overflow. The attack is local, as reflected by the AV:L vector, and does not require user interaction.

Q: Which deployments are affected?

X.Org X Server versions before 21.1.15 and XWayland versions before 24.1.14 are affected in the CopyArea CPU-to-FBO path.

Q: What is the likely impact of successful exploitation?

An attacker may crash the X server or potentially execute code in the X server context. Confidentiality, integrity, and availability are all rated high in the provided CVSS vector.

Published Oct 28, 2026

Updated

A heap buffer overflow caused by mismatched size usage in CopyArea CPU-to-FBO path in X.Org X Server before 21.1.15 and XWayland before 24.1.14 could be used by authenticated X clients to crash or potentially execute code in the X server context.

Affected Software

2 affected componentsFixes available

alpine/xorg-server<21.1.25-r0

21.1.25-r0

alpine/xwayland<24.1.14-r0

24.1.14-r0

Event History

Oct 28, 2026

CVE Published

via OSV·04:17 PM

Data Sourced

via OSV·04:17 PM

DescriptionSeverityAffected Software

Frequently Asked Questions

Who can exploit this issue?

An authenticated X client can trigger the overflow. The attack is local, as reflected by the AV:L vector, and does not require user interaction.

Which deployments are affected?

X.Org X Server versions before 21.1.15 and XWayland versions before 24.1.14 are affected in the CopyArea CPU-to-FBO path.

What is the likely impact of successful exploitation?

An attacker may crash the X server or potentially execute code in the X server context. Confidentiality, integrity, and availability are all rated high in the provided CVSS vector.

ALPINE-CVE-2026-93522: Buffer Overflow

Affected Software

Event History

Frequently Asked Questions

Who can exploit this issue?

Which deployments are affected?

What is the likely impact of successful exploitation?

Company

Resources

Contact

Frequently Asked Questions

Who can exploit this issue?

Which deployments are affected?

What is the likely impact of successful exploitation?