GPU VulnDB

Database/NVIDIA / GPU stack

Linux kernel Intel Xe dma-buf import: retry loop reuses a buffer object that was already freed

CVSS 7.8CVE-2026-52950NVIDIA / GPU stackcurated

Impact

The dma-buf import path retried after failure, but the buffer object is freed on the error return, so the retry touched freed memory - a use-after-free in the GPU driver reachable from the import ioctl. The fix restructures allocation and init into one unit so the retry operates on a live object. A kernel use-after-free driven from a render node is the classic container-to-host escalation shape on a GPU box: the attacker is already on the node and only needs the GPU device that their workload legitimately has. Red Hat has shipped errata for RHEL, which is the signal that this is being treated as a real local privilege-escalation risk rather than a tidy-up. Only hosts running drm/xe for Intel GPUs are affected.

Who can reach it

Local, authenticated. Any tenant with a /dev/dri render node on an Intel Xe GPU who can make a dma-buf import fail and retry. No remote path.

What to do

Patch to a fixed stable or distribution kernel - RHSA-2026:42919 and RHSA-2026:45192 carry it for RHEL - and reboot each affected GPU node. No live mitigation exists short of denying render-node access to untrusted workloads. Plan a drain and reboot per node; on a shared Intel GPU cloud this one is worth a dedicated window rather than waiting for the quarterly kernel roll.

References

Related entries

All NVIDIA / GPU stack entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.