# CVE-2023-52913: drm/i915: Fix potential context UAFs

> A use-after-free vulnerability in the Linux kernel's i915 driver allows local attackers to potentially execute code or escalate privileges via race conditions.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Aug 2024
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-49129, BELL-CVE-2023-52913, DEBIAN-CVE-2023-52913, GHSA-6wp2-34q6-2gfj, ROOT-OS-DEBIAN-11-CVE-2023-52913, UBUNTU-CVE-2023-52913

## What is CVE-2023-52913?

CVE-2023-52913 is a high-severity use after free vulnerability in Linux kernel, published on 21 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

drm/i915: Fix potential context UAFs

gem_context_register() makes the context visible to userspace, and which
point a separate thread can trigger the I915_GEM_CONTEXT_DESTROY ioctl.
So we need to ensure that nothing uses the ctx ptr after this.  And we
need to ensure that adding the ctx to the xarray is the *last* thing
that gem_context_register() does with the ctx pointer.

[tursulin: Stable and fixes tags add/tidy.]
(cherry picked from commit bed4b455cf5374e68879be56971c1da563bcd90c)

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2023-52913 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-52913 is a high-severity use after free vulnerability in Linux kernel, published on 21 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-52913 in the wild and no public exploit code.

Affected product: Linux kernel. 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-52913/ (Markdown: https://insights.sbomify.com/CVE-2023-52913/index.md)
```

## Sources

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

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