# CVE-2023-45922: Null dereference in n/a

> A segmentation violation in Mesa's glx_pbuffer.c allows a local attacker to cause a denial of service via crafted drawable attributes.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Mar 2024
- **Updated:** 4 Nov 2025
- **Also known as:** DEBIAN-CVE-2023-45922, ECHO-0803-b493-8054, GHSA-9gv2-h67q-4h2v

## What is CVE-2023-45922?

CVE-2023-45922 is a medium-severity vulnerability in n/a, published on 27 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

glx_pbuffer.c in Mesa 23.0.4 was discovered to contain a segmentation violation when calling __glXGetDrawableAttribute(). NOTE: this is disputed because there are no common situations in which users require uninterrupted operation with an attacker-controller server.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

## Which versions are affected by CVE-2023-45922?

It affects 1 product.


Products: Mesa3d Mesa.

## How do I fix CVE-2023-45922?

Apply the vendor's patch.

## Is CVE-2023-45922 being exploited?

There is no known exploitation of CVE-2023-45922 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2026-40393](https://insights.sbomify.com/CVE-2026-40393/): Memory corruption in Mesa (high 8.1)
- [CVE-2023-45931](https://insights.sbomify.com/CVE-2023-45931/): Null dereference in n/a (high 7.5)
- [CVE-2013-1993](https://insights.sbomify.com/CVE-2013-1993/): Integer overflow in n/a (medium 6.8)
- [CVE-2023-45913](https://insights.sbomify.com/CVE-2023-45913/): Null dereference in n/a (medium 6.2)
- [CVE-2023-45919](https://insights.sbomify.com/CVE-2023-45919/): Memory corruption in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-45922 and fix it if it is affected.

What it is: CVE-2023-45922 is a medium-severity vulnerability in n/a, published on 27 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-45922 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-45922/ (Markdown: https://insights.sbomify.com/CVE-2023-45922/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-45922
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-45922
- OSV: https://osv.dev/vulnerability/CVE-2023-45922

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-45922/
Summaries are generated and may contain mistakes; the official description above is the record.