cve.bz

CVE-2026-52951 linux linux kernel: Use After Free

7.8 highEPSS 0.2%Fix available

High (7.8) in linux linux kernel. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: drm/xe/dma-buf: handle empty bo and UAF races There look to be some nasty races here when triggering the invalidate_mappings hook: 1) We do xe_bo_alloc() followed by the attach, before the actual full bo init step in xe_dma_buf_init_obj(). However the bo is visible on the attachments list after the attach. This is bad since exporter driver, say amdgpu, can at any time call back into our invalidate_mappings hook, with an empty/bogus bo, leading to potential bugs/crashes. 2) Similar to 1) but here we get a UAF, when the invalidate_mappings hook is triggered. For example, we get as far as xe_bo_init_locked() but this fails in some way. But here the bo will be freed on error, but we still have it attached from dma-buf pov, so if the invalidate_mappings is now triggered then the bo we access is gone and we trigger UAF and more bugs/crashes. To fix this, move the attach step until after we actually have a fully set up buffer object. Note that the bo is not published to userspace until later, so not sure what the comment "Don't publish the bo until we have a valid attachment", is referring to. We have at least two different customers reporting hitting a NULL ptr deref in evict_flags when importing something from amdgpu, followed by triggering the evict flow. Hit rate is also pretty low, which would hint at some kind of race, so something like 1) or 2) might explain this. v2: - Shuffle the order of the ops slightly (no functional change) - Improve the comment to better explain the ordering (Matt B) (cherry picked from commit af1f2ad0c59fe4e2f924c526f66e968289d77971)

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-416 Use After Free
CWE-476 NULL Pointer Dereference
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-52951 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-52951?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-52951?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-52951 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.8 and later

Fixed in

ProductRelease lineFixed in
Linux6.126.12.91
Linux6.186.18.33
Linux7.07.0.10
Linuxlater releases7.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13linux6.12.94-1DEBIAN-CVE-2026-52951
Debian14linux7.0.10-1DEBIAN-CVE-2026-52951
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-52951
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-52951
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-52951
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1061.64~22.04.1UBUNTU-CVE-2026-52951 USN-8595-3
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1063.71~22.04.1UBUNTU-CVE-2026-52951 USN-8606-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1062.69~22.04.1UBUNTU-CVE-2026-52951 USN-8609-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1064.72~22.04.1UBUNTU-CVE-2026-52951 USN-8567-1
Ubuntu22.04:LTSlinux-hwe-6.86.8.0-136.136~22.04.1UBUNTU-CVE-2026-52951 USN-8619-1
Ubuntu22.04:LTSlinux-ibm-6.86.8.0-1061.62~22.04.1UBUNTU-CVE-2026-52951 USN-8574-3
Ubuntu22.04:LTSlinux-lowlatency-hwe-6.86.8.0-136.136.2~22.04.1UBUNTU-CVE-2026-52951 USN-8574-2
Ubuntu22.04:LTSlinux-nvidia-6.86.8.0-1059.62~22.04.1UBUNTU-CVE-2026-52951 USN-8596-1
Ubuntu22.04:LTSlinux-oracle-6.86.8.0-1058.61~22.04.1UBUNTU-CVE-2026-52951 USN-8595-1
44 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 15 SP7, Linux Enterprise Live Patching 15 SP7, Linux Enterprise Module for Legacy 15 SP7 and 1 morekernel-default6.4.0-150700.53.73.2SUSE-SU-2026:3166-1
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.37.1SUSE-SU-2026:23237-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7-RT_Update_181-150700.1.5.1SUSE-SU-2026:3130-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_191-150700.15.3.4SUSE-SU-2026:3166-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-64kb, kernel-default, kernel-zfcpdump6.4.0-150700.53.73.2SUSE-SU-2026:3166-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-default-base6.4.0-150700.53.73.2.150700.17.41.4SUSE-SU-2026:3166-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-source6.4.0-150700.53.73.1SUSE-SU-2026:3166-1
SUSELinux Enterprise Module for Development Tools 15 SP7kernel-docs, kernel-syms, kernel-source6.4.0-150700.53.73.1SUSE-SU-2026:3166-1
SUSELinux Enterprise Module for Development Tools 15 SP7kernel-obs-build6.4.0-150700.53.73.2SUSE-SU-2026:3166-1
SUSELinux Enterprise Module for Public Cloud 15 SP7kernel-azure6.4.0-150700.53.73.2SUSE-SU-2026:3166-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-64kb, kernel-docs, kernel-syms and 6 more6.12.0-160000.37.1SUSE-SU-2026:23221-1 SUSE-SU-2026:23231-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-default-base6.12.0-160000.37.1.160000.2.19SUSE-SU-2026:23221-1 SUSE-SU-2026:23231-1
4 more for SUSE in the JSON and on SUSE's page.
openSUSELeap 16.0kernel-default-base6.12.0-160000.37.1.160000.2.19openSUSE-SU-2026:21555-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160000.37.1openSUSE-SU-2026:21555-1
Alpaquita25linux-lts6.12.92-r0BELL-CVE-2026-52951
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2026-52951

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Important.

Red Hat's statement

A flaw rated IMPORTANT by Red Hat was found in the Linux kernel drm/xe dma-buf buffer object handling, affecting Red Hat Enterprise Linux 9 and 10 (kernel and kernel-rt) and Red Hat In-Vehicle OS 2 streams that contain the Xe driver; a fix is being pursued for those affected streams. In the dma-buf import path, the buffer object is attached and made visible on the attachments list before it is fully initialized in xe_dma_buf_init_obj(), and on error paths a buffer object that has already been freed can remain attached. If an exporter driver, such as amdgpu, then calls back into the invalidate_mappings hook, that hook can be invoked with an empty, bogus, or freed buffer object, triggering a NULL pointer dereference in the evict path or a use-after-free that crashes the kernel. A local low-privileged attacker able to trigger these dma-buf import and eviction sequences could therefore cause a denial of service, although successful exploitation requires winning a race with complex timing (attack complexity is high). Red Hat Enterprise Linux 6, 7, and 8, as well as the Red Hat Enterprise Linux 9.2 and 9.4 update streams, are not affected because the vulnerable code is not present in those kernels. Red Hat and CVE.org both rate this flaw CVSS 3.1 7.0 (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), so there is no difference from the upstream severity.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelAffected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelAffected
Red Hat Enterprise Linux 9kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-52951.

References

Check your stackJSON