CVE-2024-46705

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.

A flaw was found in the Linux kernel drm/xe (Intel Xe graphics) driver, rated low impact by Red Hat. The driver did not reset its memory-mapped I/O (MMIO) mappings to NULL after device removal, so code that subsequently accessed MMIO registers could hit an address range that had already been unmapped and potentially remapped for another use, resulting in memory corruption or a system crash. Red Hat scored this flaw CVSS 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), reflecting availability impact only from a local, privilege-required position; this is lower than the CVE.org score of 7.8, which additionally assumes confidentiality and integrity impact. The vulnerable drm/xe driver code is not present in the Red Hat Enterprise Linux 6, 7, 8, and 9 kernels, so all Red Hat Enterprise Linux kernel and kernel-rt streams and the Hosted OpenShift clusters are recorded as not affected. The issue affects the community Fedora kernel, where a fix is being pursued through the delegated community update process; the Fedora kernel update containing the fix has been released.

The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational purposes to better understand the severity of this vulnerability.