dbcve.org
Linux KernelOperating system · Linux

CVE-2026-52950

HIGH · 7.8 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 6.18.33 / 7.0.10 or later.
See remediation →
80/100
Remediation priority · High
Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A Use-After-Free (UAF) vulnerability exists in the Linux kernel's DRM Xe driver dma-buf handling. The retry loop logic fails because the buffer object (bo) gets freed on error, creating a UAF condition when retry attempts to use the freed object. The fix restructures the code to perform allocation and initialization as a combined unit before attachment, making the retry mechanism safe.

MitigationApply the kernel patch (commit 479669418253e0f27f8cf5db01a731352ea592e7) to restructure the alloc+init sequence in the Xe dma-buf code. This is a code-level fix requiring kernel source modification and rebuild.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 6.18, < 6.18.33>= 6.19, < 7.0.10= 7.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check kernel version
    Run 'uname -r' or check /proc/version to get the running kernel version. Compare against affected ranges: 6.18.x where x >= 0 and x < 33; 6.19.x where x >= 0 and x < 10; 7.1.x where x >= 0
    Affected if Kernel version falls within 6.18.0-6.18.32, 6.19.0-7.0.9, or 7.1.x
  2. Verify Xe DRM driver presence
    Check if the Xe driver is loaded or built into the kernel by running 'ls /sys/class/drm/' and looking for 'card*' entries, or check 'modinfo i915' (Xe is part of i915/Xe driver stack) or check kernel config for CONFIG_DRM_XE
    Affected if System has Intel Xe GPU hardware and the Xe DRM driver is available
  3. Confirm dma-buf usage with Xe driver
    Monitor for dma-buf operations involving Xe buffer objects. This typically occurs during GPU memory sharing between processes or devices. Check dmesg for related errors, or use 'ls -la /proc/*/fd' to look for dma-buf file descriptors if Xe buffers are actively in use
    Affected if Any workload using dma-buf sharing with Xe GPU buffers is running on a vulnerable kernel
  4. Identify specific vulnerable code path
    The vulnerability occurs in the dma-buf attachment retry logic in the Xe driver. This typically manifests during buffer export/import operations. Check dmesg for 'use-after-free' or 'drm' related errors, particularly after failed dma-buf operations
    Affected if Use-after-free errors appear in kernel logs related to Xe DRM driver dma-buf handling

A system is affected if it runs a vulnerable Linux kernel version (6.18.x before 6.18.33, 6.19.x before 7.0.10, or 7.1.x) on Intel Xe GPU hardware and actively uses the Xe DRM driver for dma-buf operations

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.18.33 / 7.0.10 or later
Fixed in 6.18.337.0.10
Interim mitigation

Apply the kernel patch (commit 479669418253e0f27f8cf5db01a731352ea592e7) to restructure the alloc+init sequence in the Xe dma-buf code. This is a code-level fix requiring kernel source modification and rebuild.

Recommended fix High confidence

6.18.33 for 6.18.x; 7.0.10 for 6.19.x and 7.1.x

  1. 1. Identify the current running Linux kernel version using `uname -r`
  2. 2. For kernels in the 6.18.x branch: upgrade to kernel version 6.18.33 or later
  3. 3. For kernels in the 6.19.x branch: upgrade to kernel version 7.0.10 or later
  4. 4. For kernels in the 7.1.x branch: upgrade to kernel version 7.0.10 or later
  5. 5. After upgrading, verify the fix is applied by checking the kernel version matches or exceeds the fixed version for your branch
  6. 6. Reboot the system to load the new kernel
Caveat Kernel upgrades may require matching system utilities and drivers; ensure compatibility with hardware and custom modules before upgrading production systems

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-52950 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-52950 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data