Vulnerability Description
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)
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.8, < 6.10.11 |
Related Weaknesses (CWE)
References
- https://git.kernel.org/stable/c/94c4aa266111262c96c98f822d1bccc494786feePatch
- https://git.kernel.org/stable/c/abc8feacacf8fae10eecf6fea7865e8c1fee419cPatch
FAQ
What is CVE-2024-46866?
CVE-2024-46866 is a vulnerability with a CVSS score of 5.5 (MEDIUM). 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, howev...
How severe is CVE-2024-46866?
CVE-2024-46866 has been rated MEDIUM with a CVSS base score of 5.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2024-46866?
Check the references section above for vendor advisories and patch information. Affected products include: Linux Linux Kernel.