First published: Fri Sep 27 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: drm/xe/client: add missing bo locking in show_meminfo() bo_meminfo() 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 bo_meminfo(), ensuring we drop any spinlocks first. In the case of object_idr we now also need to hold a ref. v2 (MattB) - Also add xe_bo_assert_held() (cherry picked from commit 4f63d712fa104c3ebefcb289d1e733e86d8698c7)
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | >=6.8<6.10.11 | |
Linux Kernel | =6.11-rc1 | |
Linux Kernel | =6.11-rc2 | |
Linux Kernel | =6.11-rc3 | |
Linux Kernel | =6.11-rc4 | |
Linux Kernel | =6.11-rc5 | |
Linux Kernel | =6.11-rc6 | |
Linux Kernel | =6.11-rc7 | |
debian/linux | 5.10.223-1 5.10.234-1 6.1.129-1 6.1.135-1 6.12.22-1 6.12.25-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-46866 is considered to be of medium severity due to potential null pointer dereferences and use-after-free vulnerabilities.
To fix CVE-2024-46866, update to a patched version of the Linux kernel, such as 5.10.223-1 or newer.
CVE-2024-46866 affects Linux kernel versions from 6.8 to 6.10.11 and specific 6.11 release candidates.
Systems running the affected versions of the Linux kernel, particularly those using graphics drivers or utilizing the DRM subsystem, are at risk.
Currently, there are no known effective workarounds for CVE-2024-46866; updating the kernel is the recommended action.