CVE-2025-49178: Xorg-x11-server-xwayland: xorg-x11-server: tigervnc: unprocessed client request due to bytes to ignore
A flaw was found in the X server's request handling. Non-zero 'bytes to ignore' in a client's request can cause the server to skip processing another client's request, potentially leading to a denial of service.
Security readout for executives and security teams
Plain-English summary
This is a denial-of-service issue in X server request handling. A low-privileged local client can disrupt processing of another client’s request, potentially making graphical sessions or VNC-backed workflows unavailable. It does not indicate data theft or code execution in the supplied sources.
Executive priority
Treat as a moderate availability risk. It is not a known active exploitation emergency from the supplied evidence, but shared Linux graphical environments should be patched in normal security maintenance windows, sooner where outages would affect operations.
Technical view
The flaw involves non-zero “bytes to ignore” handling in client requests. Affected Xorg/Xwayland/TigerVNC server components may skip another client request, causing availability impact. CVSS 3.1 is 5.5 with AV:L/PR:L/UI:N and availability high.
Likely exposure
Exposure is most likely on Red Hat systems running affected xorg-x11-server, xorg-x11-server-Xwayland, or TigerVNC packages, especially multi-user desktops, graphical servers, VDI, or VNC environments where low-privileged users can access sessions.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. The CVSS vector indicates local access with low privileges is required, no user interaction is needed, and the impact is limited to availability.
Researcher notes
Evidence is strongest for Red Hat package streams and the CVE description. The bundle does not provide proof-of-concept details, exploit telemetry, or upstream fixed-version specifics beyond RHSA references. Avoid assuming remote exploitation despite TigerVNC package impact.
Mitigation direction
Identify affected Red Hat package versions across RHEL and lifecycle add-on environments.
Apply the applicable Red Hat RHSA updates for each affected package stream.
Prioritize shared graphical, VDI, and TigerVNC systems with untrusted or many users.
Check vendor guidance for any stream-specific remediation or support constraints.
Validation and detection
Inventory installed xorg-x11-server, Xwayland, and TigerVNC package versions.
Map hosts to affected RHEL versions and lifecycle channels listed in the CVE bundle.
Confirm relevant Red Hat errata are installed or scheduled for deployment.
Review service exposure for shared graphical sessions and VNC usage.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-667: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-667 · source CWE mapping
Improper Locking
Improper Locking represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.