# CVE-2023-52913: linux: In the Linux kernel, the following vulnerability has been resolved:  drm/i915: Fix potential context UAFs  gem_contex...

CVE-2023-52913 is fixed in linux on 1 platform, first by DEBIAN-CVE-2023-52913, released August 21, 2024. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2023-52913
- Priority: Routine
- CVSS: 5.5 (medium)
- EPSS: 0.0025
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Aug 21, 2024

## 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)

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 12.15 (bookworm) | 6.1.7-1 | [DEBIAN-CVE-2023-52913](https://patchblox.com/security/data/fix/linux/debian-cve-2023-52913.md) | Aug 21, 2024 |
| Linux | linux Debian 13.5 (trixie) | 6.1.7-1 | [DEBIAN-CVE-2023-52913](https://patchblox.com/security/data/fix/linux/debian-cve-2023-52913.md) | Aug 21, 2024 |
| Linux | linux Debian 14 | 6.1.7-1 | [DEBIAN-CVE-2023-52913](https://patchblox.com/security/data/fix/linux/debian-cve-2023-52913.md) | Aug 21, 2024 |

---

Data as of 2026-11-09T01:18:40Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.