CVE-2023-52913

Modified
Published: 21 Aug 2024, 06:10
Last modified:11 May 2026, 19:35

Vulnerability Summary

Overall Risk (default)
low
22/100
CVSS Score
5.5 MEDIUM
v3.1 (nvd)
EPSS Score
0.01% LOW
0% probability 0.00%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

21 Aug 2024, 06:10
Published
Vulnerability first disclosed
11 May 2026, 19:35
Last Modified
Vulnerability information updated

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)

CVSS Metrics

  • v3.1MEDIUMScore: 5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS Trends

Current EPSS score: 0.01% Percentile: 3%

Techniques & Countermeasures

  • CWE-416Use After Free

    The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Affected Systems

  • linuxlinux

    ≥ eb4dedae920a07c485328af3da2202ec5184fb17, < ae278887193110dfeb857ea63e243a3851fbb0bc | ≥ eb4dedae920a07c485328af3da2202ec5184fb17, < b696c627b3f56e173f7f70b8487d66da8ff22506 | ≥ eb4dedae920a07c485328af3da2202ec5184fb17, < afce71ff6daa9c0f852df0727fe32c6fb107f0fa | 5.10

  • linuxlinux_kernel

    ≥ 5.8.11, < 5.9 | ≥ 5.10, < 6.1.7 | 6.2:rc1 | 6.2:rc2 | 6.2:rc3

References (3)