First published: Mon Oct 21 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: drm/xe/ct: prevent UAF in send_recv() Ensure we serialize with completion side to prevent UAF with fence going out of scope on the stack, since we have no clue if it will fire after the timeout before we can erase from the xa. Also we have some dependent loads and stores for which we need the correct ordering, and we lack the needed barriers. Fix this by grabbing the ct->lock after the wait, which is also held by the completion side. v2 (Badal): - Also print done after acquiring the lock and seeing timeout. (cherry picked from commit 52789ce35c55ccd30c4b67b9cc5b2af55e0122ea)
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | >=6.8<6.11.4 | |
Linux Kernel | =6.12-rc1 | |
Linux Kernel | =6.12-rc2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-50030 is rated as a high severity vulnerability due to its potential for causing user-after-free conditions.
To fix CVE-2024-50030, update the Linux kernel to version 6.11.4 or later, or ensure you are using the latest release version above 6.12-rc2.
CVE-2024-50030 affects Linux kernel versions from 6.8 up to and including 6.11.4, as well as specific 6.12 release candidates.
CVE-2024-50030 is a user-after-free vulnerability that occurs in the send_recv() function of the Linux kernel.
As of now, there are no publicly known exploits specifically targeting CVE-2024-50030.