CVE-2024-50144: drm/xe: fix unbalanced rpm put() with fence_fini()
First published: Thu Nov 07 2024(Updated: )
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)
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | >=6.11<6.11.6 | |
| Linux Kernel | =6.12-rc1 | |
| Linux Kernel | =6.12-rc2 | |
| Linux Kernel | =6.12-rc3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/046bd018c0123b1a49c22abed5f9ea31d1454c78
- https://git.kernel.org/stable/c/03a86c24aea0920a1ca20a0d7771d5e176db538d
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50144
- https://nvd.nist.gov/vuln/detail/CVE-2024-50144
- https://launchpad.net/bugs/cve/CVE-2024-50144
- https://security-tracker.debian.org/tracker/CVE-2024-50144
- https://ubuntu.com/security/CVE-2024-50144
Frequently Asked Questions
What is the severity of CVE-2024-50144?
CVE-2024-50144 is classified as a medium severity vulnerability in the Linux kernel.
How do I fix CVE-2024-50144?
To fix CVE-2024-50144, update to the patched versions of the Linux kernel, specifically 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.128-1, 6.12.12-1, or 6.12.15-1.
What systems are affected by CVE-2024-50144?
CVE-2024-50144 affects various versions of the Linux kernel, specifically versions between 6.11 and 6.12-rc3.
What kind of attacks can exploit CVE-2024-50144?
CVE-2024-50144 could potentially allow local attackers to manipulate kernel memory management, leading to system instability.
Is there a workaround for CVE-2024-50144 if I cannot upgrade?
There are no specific workarounds mentioned for CVE-2024-50144, so upgrading is the recommended action to mitigate the vulnerability.
- agent/title
- agent/references
- agent/description
- agent/type
- agent/first-publish-date
- agent/author
- agent/event
- agent/remedy
- agent/severity
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/softwarecombine
- agent/tags
- collector/usn-cve
- source/Ubuntu
- vendor/linux
- canonical/linux kernel
- version/linux kernel/6.11
- version/linux kernel/6.12-rc1
- version/linux kernel/6.12-rc2
- version/linux kernel/6.12-rc3