CVE-2024-46866: drm/xe/client: add missing bo locking in show_meminfo()
In the Linux kernel, the following vulnerability has been resolved:
drm/xe/client: add missing bo locking in showmeminfo()
bomeminfo() wants to inspect bo state like tt and the ttm resource, however this state can change at any point leading to stuff like NPD and UAF, if the bo lock is not held. Grab the bo lock when calling bomeminfo(), ensuring we drop any spinlocks first. In the case of objectidr we now also need to hold a ref.
v2 (MattB) - Also add xeboassertheld()
(cherry picked from commit 4f63d712fa104c3ebefcb289d1e733e86d8698c7)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-46866?
CVE-2024-46866 is considered to be of medium severity due to potential null pointer dereferences and use-after-free vulnerabilities.
How do I fix CVE-2024-46866?
To fix CVE-2024-46866, update to a patched version of the Linux kernel, such as 5.10.223-1 or newer.
Which versions of the Linux kernel are affected by CVE-2024-46866?
CVE-2024-46866 affects Linux kernel versions from 6.8 to 6.10.11 and specific 6.11 release candidates.
What types of systems are at risk due to CVE-2024-46866?
Systems running the affected versions of the Linux kernel, particularly those using graphics drivers or utilizing the DRM subsystem, are at risk.
Is there a workaround for CVE-2024-46866?
Currently, there are no known effective workarounds for CVE-2024-46866; updating the kernel is the recommended action.