CVE-2026-52951 remediation guide

Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6

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 inval...

Open CVE record

ProductLinux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6

Affected versions>= dd08ebf6c3525a7ea2186e636df064ea47281987 < 9894731e513019df22a29e5c52f1c98890355ff1, >= dd08ebf6c3525a7ea2186e636df064ea47281987 < 20a99ea1e2fd720856d6ba497ff26b82c604751f, >= dd08ebf6c3525a7ea2186e636df064ea47281987 < c473ae25421fddc3dde247ba7b85225b10641d09, >= dd08ebf6c3525a7ea2186e636df064ea47281987 < 981bedbbe61364fcc3a3b87ebaf648a66cd07108, >= 6.8, >= 6.8 < 6.12.91, >= 6.13 < 6.18.33, >= 6.19 < 7.0.10, 7.1

Fixed versions6.12.91, 6.18.33, 7.0.10

Priority basisReview · CVSS 7.8 · EPSS 0.14%

Identify the affected asset

Confirm whether Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6 is installed, record the deployed version and installation path, and identify exposed interfaces.

Record the product name, package or appliance identifier, and installed version.
Identify internet-facing, administrative, API, and internal access paths.
Preserve the pre-change configuration and relevant service logs.

Validate the affected-version match

Compare the deployed version with the affected range: >= dd08ebf6c3525a7ea2186e636df064ea47281987 < 9894731e513019df22a29e5c52f1c98890355ff1, >= dd08ebf6c3525a7ea2186e636df064ea47281987 < 20a99ea1e2fd720856d6ba497ff26b82c604751f, >= dd08ebf6c3525a7ea2186e636df064ea47281987 < c473ae25421fddc3dde247ba7b85225b10641d09, >= dd08ebf6c3525a7ea2186e636df064ea47281987 < 981bedbbe61364fcc3a3b87ebaf648a66cd07108, >= 6.8, >= 6.8 < 6.12.91, >= 6.13 < 6.18.33, >= 6.19 < 7.0.10, 7.1. Treat incomplete inventory results as unresolved.

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 6.12.91, 6.18.33, 7.0.10. Preserve configuration and rollback material before change.

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

Confirm the expected version and package state.
Run a functional health check for critical service paths.
Review authentication, error, application, and security monitoring logs.
Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.