GLX client crash via untrusted attribute count
Published Mar 27, 2024 · Updated Nov 4, 2025
Buffer over-read in Mesa 23.0.4 allows context-dependent attackers controlling an X server to crash a GLX client. In __glXGetDrawableAttribute(), glx_pbuffer.c trusts the reply's numAttribs field, allocates from a different length, and indexes data twice per claimed attribute. Exploitation requires a client to query a missing attribute through an attacker-controlled X server; the CVE is disputed because this availability requirement is uncommon.
Summary
What happened
Buffer over-read in Mesa 23.0.4 allows context-dependent attackers controlling an X server to crash a GLX client. In __glXGetDrawableAttribute(), glx_pbuffer.c trusts the reply's numAttribs field, allocates from a different length, and indexes data twice per claimed attribute. Exploitation requires a client to query a missing attribute through an attacker-controlled X server; the CVE is disputed because this availability requirement is uncommon.
The record
- CVE
- CVE-2023-45922
- Published
- Mar 27, 2024
- Updated
- Nov 4, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-754, T1499
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 27, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo