CVE-2026-52976 remediation guide
Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 9
In the Linux kernel, the following vulnerability has been resolved: drm/xe: Fix error cleanup in xe_exec_queue_create_ioctl() Two error handling issues exist in xe_exec_queue_create_ioctl(): 1. When xe_hw_engine_group_add_exec_queue() fails, the error path jumps to put_exec_queue which skips xe_exec_queue_kill(). If the VM is in preempt fence mode, xe_vm_add_compute_exec_queue() has already added the queue to the VM's compute exec queue list. Skipping the kill leaves the queue on that list, leading to a dangling pointer after the queue is freed. 2. When xa_alloc() fails after xe_hw_engine_g...
Identify the affected asset
Confirm whether Linux Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 9 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: >= 7970cb36966c9b9183255dc097ae0446300eebcf < f93b00161213a0fe9f7ff1d8498ee5ca9e0a5c43, >= 7970cb36966c9b9183255dc097ae0446300eebcf < 753b149d5a433eb19e0c1b0eb4526a6e26120d1f, >= 7970cb36966c9b9183255dc097ae0446300eebcf < 1be55646d8a2035343b012dcb12210db7bb8b056, >= 7970cb36966c9b9183255dc097ae0446300eebcf < f3cc22d4df3ed58439ea7e21daa54c3608e03b78, >= 6.12, >= 6.12 < 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.