drm/xe: reset mmio mappings with devm
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: reset mmio mappings with devm
Set our various mmio mappings to NULL. This should make it easier to catch something rogue trying to mess with mmio after device removal. For example, we might unmap everything and then start hitting some mmio address which has already been unmamped by us and then remapped by something else, causing all kinds of carnage.
From the CVE record · Linux
The Linux kernel's drm/xe component may access MMIO after a device is removed and its mappings are unmapped. This could cause unintended access to memory remapped by something else. The input does not establish an attacker path or specify authentication or user-interaction requirements.
Engineers running Linux kernels with the drm/xe component should check their versions; affected versions are not specified.