CVE-2024-50144
Last modified
CVE-2024-50144 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: drm/xe: fix unbalanced rpm put() with fence_fini() Currently we can call fence_fini() twice if something goes wrong when sending the GuC CT for the tlb request, since we signal the fence and return an error, leading to the caller also calling fini() on the error path in the case of stack version of the flow, which leads to an extra rpm put() which might later cause device to enter suspend when it shouldn't. It looks like we can just drop the fini() call since the fence signaller side will already call this for us. There are known mysterious splats with device going to sleep even with an rpm ref, and this could be one candidate. v2 (Matt B): - Prefer warning if we detect double fini() (cherry picked from commit cfcbc0520d5055825f0647ab922b655688605183). EPSS estimates a 0.20% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: drm/xe: fix unbalanced rpm put() with fence_fini() Currently we can call fence_fini() twice if something goes wrong when sending the GuC CT for the tlb request, since we signal the fence and return an error, leading to the caller also calling fini() on the error path in the case of stack version of the flow, which leads to an extra rpm put() which might later cause device to enter suspend when it shouldn't. It looks like we can just drop the fini() call since the fence signaller side will already call this for us. There are known mysterious splats with device going to sleep even with an rpm ref, and this could be one candidate. v2 (Matt B): - Prefer warning if we detect double fini() (cherry picked from commit cfcbc0520d5055825f0647ab922b655688605183)
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.11, < 6.11.6 | — |
| Linux | Linux Kernel | 6.12 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-50144?
How severe is CVE-2024-50144?
How do I fix CVE-2024-50144?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-50139In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-5014In WhatsUp Gold versions released before 2023.1.3, a Server …6.5
- CVE-2024-50140In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50141In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50142In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50143In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-50145In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50146In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50147In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50148In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50149In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-5015In WhatsUp Gold versions released before 2023.1.3, an authen…8.8
Are you affected by CVE-2024-50144?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
