CVE-2026-46309 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/uapi: Reject coh_none PAT index for CPU cached memory in madvise Add validation in xe_vm_madvise_ioctl() to reject PAT indices with XE_COH_NONE coherency mode when applied to CPU cached memory. Using coh_none with CPU cached buffers is a security issue. When the kernel clears pages before reallocation, the clear operation stays in CPU cache (dirty). GPU with coh_none can bypass CPU caches and read stale sensitive data directly from DRAM, potentially leaking data from previously freed pages of other processes. This al...
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: >= ada7486c5668db542a7d361268df931aca5b726a < 87f9b1528e1ffc1da3615d552c9a06aba5e20b00, >= ada7486c5668db542a7d361268df931aca5b726a < fea04cf6f2345bc50f15b6638906c35962b89424, >= ada7486c5668db542a7d361268df931aca5b726a < 4e5591c2fc1b30f4ea5e2eab4c3a695acc404e39, >= 6.18, >= 6.18 < 6.18.32, >= 6.19 < 7.0.9, 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.18.32, 7.0.9. 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.