# CVE-2023-54202: drm/i915: fix race condition UAF in i915_perf_add_config_ioctl

> A race condition in the Linux kernel's i915 driver allows local attackers to trigger a use-after-free, potentially leading to code execution or privilege escalation.

- **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:** 30 Dec 2025
- **Updated:** 15 Oct 2026
- **Also known as:** BELL-CVE-2023-54202, DEBIAN-CVE-2023-54202, GHSA-2x24-vjrm-p9g2, ROOT-OS-DEBIAN-11-CVE-2023-54202, UBUNTU-CVE-2023-54202

## What is CVE-2023-54202?

CVE-2023-54202 is a high-severity use after free vulnerability in Linux, published on 30 Dec 2025. 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 race condition UAF in i915_perf_add_config_ioctl

Userspace can guess the id value and try to race oa_config object creation
with config remove, resulting in a use-after-free if we dereference the
object after unlocking the metrics_lock.  For that reason, unlocking the
metrics_lock must be done after we are done dereferencing the object.

[tursulin: Manually added stable tag.]
(cherry picked from commit 49f6f6483b652108bcb73accd0204a464b922395)

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


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

Apply the vendor's patch.

## Is CVE-2023-54202 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-54202 is a high-severity use after free vulnerability in Linux, published on 30 Dec 2025. 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-54202 in the wild and no public exploit code.

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

## Sources

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

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