CVE-2026-52950
Medium
Elevated severity or exploit probability.
CVSS base
7.8
HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS — probability of exploitation (30 days)
0.1%
3.6th percentile
CISA KEV
Not listed
Weakness / dates
CWE-825
Published 2026-06-24 · modified 2026-07-27
CVSS breakdown
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
| Attack Vector | L | Local |
| Attack Complexity | L | Low |
| Privileges Required | L | Low |
| User Interaction | N | None |
| Scope | U | Unchanged |
| Confidentiality | H | High |
| Integrity | H | High |
| Availability | H | High |
Timeline
- 2026-06-24 — Published (NVD)
- 2026-07-27 — Last modified (NVD)
Description
In the Linux kernel, the following vulnerability has been resolved: drm/xe/dma-buf: fix UAF with retry loop Retry doesn't work here, since bo will be freed on error, leading to UAF. However, now that we do the alloc & init before the attach, we can now combine this as one unit and have the init do the alloc for us. This should make the retry safe. Reported by Sashiko. v2: Fix up the error unwind (CI) (cherry picked from commit 479669418253e0f27f8cf5db01a731352ea592e7)
Affected
References
- https://git.kernel.org/stable/c/155a372a1cc50fa93387c5d3cdfd614a61e1afd1
- https://git.kernel.org/stable/c/39fdac6be02eb7c3460518c1c4085f75f935c4ce
- https://git.kernel.org/stable/c/827062952ed9bdf4220466c1f05ce452d04bdedf
- https://access.redhat.com/errata/RHSA-2026:42919
- https://access.redhat.com/errata/RHSA-2026:45192
- https://access.redhat.com/security/cve/CVE-2026-52950
- https://bugzilla.redhat.com/show_bug.cgi?id=2492318
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-52950.json