drm/xe: Check pat.ops before dumping PAT settings
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/xe: Check pat.ops before dumping PAT settings
We may leave pat.ops unset when running on brand new platform or when running as a VF. While the former is unlikely, the latter is valid (future) use case and will cause NPD when someone will try to dump PAT settings by debugfs.
It's better to check pointer to pat.ops instead of specific .dump hook, as we have this hook always defined for every .ops variant.
From the CVE record · Linux
The Linux kernel’s drm/xe driver may leave pat.ops unset on a new platform or when running as a VF. Someone able to dump PAT settings through debugfs under those conditions can trigger a null pointer dereference. The input does not specify authentication requirements.
Engineers running Linux kernels with the drm/xe driver should check their deployments; affected versions are not specified.