https://vulnerability.circl.lu/sightings/feed 2026-05-10T06:13:10.031921+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/d6e03b87-f1b2-4223-9a41-328db138bee9/export 2026-05-10T06:13:10.401154+00:00 Automation user http://vulnerability.circl.lu/user/automation {"uuid": "d6e03b87-f1b2-4223-9a41-328db138bee9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-52913", "type": "seen", "source": "https://t.me/cvedetector/3739", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2023-52913 - Intel Linux DRM UAF Vulnerability\", \n \"Content\": \"CVE ID : CVE-2023-52913 \nPublished : Aug. 21, 2024, 7:15 a.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \ndrm/i915: Fix potential context UAFs \n \ngem_context_register() makes the context visible to userspace, and which \npoint a separate thread can trigger the I915_GEM_CONTEXT_DESTROY ioctl. \nSo we need to ensure that nothing uses the ctx ptr after this. And we \nneed to ensure that adding the ctx to the xarray is the *last* thing \nthat gem_context_register() does with the ctx pointer. \n \n[tursulin: Stable and fixes tags add/tidy.] \n(cherry picked from commit bed4b455cf5374e68879be56971c1da563bcd90c) \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"21 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-21T09:52:00.000000Z"} 2024-08-21T09:52:00+00:00