CVE-2024-50030: drm/xe/ct: prevent UAF in send_recv()

Published Oct 21, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

drm/xe/ct: prevent UAF in sendrecv()

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)

Other sources

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

4 affected componentsFixes available
Linux Linux kernel>=6.8<6.11.4
Linux Linux kernel=6.12-rc1
Linux Linux kernel=6.12-rc2
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.22-16.12.25-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to 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.22-1Fixed in 6.12.25-1

Event History

Oct 21, 2024
CVE Published
via MITRE·07:39 PM
Data Sourced
via MITRE·07:39 PM
DescriptionSeverity
Data Sourced
via NVD·08:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Feb 20, 2025
Data Sourced
via Launchpad·12:44 AM
Description
May 3, 2025
Data Sourced
via Ubuntu·12:55 AM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-50030?

CVE-2024-50030 is rated as a high severity vulnerability due to its potential for causing user-after-free conditions.

2

How do I fix CVE-2024-50030?

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.

3

Which Linux kernel versions are affected by CVE-2024-50030?

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.

4

What type of vulnerability is CVE-2024-50030?

CVE-2024-50030 is a user-after-free vulnerability that occurs in the send_recv() function of the Linux kernel.

5

Is there a known exploit for CVE-2024-50030?

As of now, there are no publicly known exploits specifically targeting CVE-2024-50030.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203