Vulnerability in Linux
CVE-2024-46866
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)
EPSS: 0.001 (3.8th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 7.8 (High). Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
Affected products
- Linux — versions 0845233388f8a26d00acf9bf230cfd4f36aa4c30, 6.8, 0
- Linux Linux_kernel — versions 6.11
Weakness classification (CWE)
Public proof-of-concept exploits
References
Frequently asked questions
- What is CVE-2024-46866?
- CVE-2024-46866 is a high-severity vulnerability in Linux, classified under Improper Locking. CVSS score: 7.8/10. Published 2024-09-27.
- How severe is CVE-2024-46866?
- High severity. CVSS v3 base score is 7.8 out of 10.
- Is CVE-2024-46866 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.