CVE-2024-50187: drm/vc4: Stop the active perfmon before being destroyed
In the Linux kernel, the following vulnerability has been resolved:
drm/vc4: Stop the active perfmon before being destroyed
Upon closing the file descriptor, the active performance monitor is not stopped. Although all perfmons are destroyed in vc4perfmonclosefile(), the active performance monitor's pointer (vc4->activeperfmon) is still retained.
If we open a new file descriptor and submit a few jobs with performance monitors, the driver will attempt to stop the active performance monitor using the stale pointer in vc4->activeperfmon. However, this pointer is no longer valid because the previous process has already terminated, and all performance monitors associated with it have been destroyed and freed.
To fix this, when the active performance monitor belongs to a given process, explicitly stop it before destroying and freeing it.
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
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1 - Upgrade
Upgrade
debian/linux-6.1to a version that resolves this vulnerability.Fixed in 6.1.129-1~deb11u1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-50187?
CVE-2024-50187 is classified as a vulnerability in the Linux kernel that may impact system performance and stability.
How do I fix CVE-2024-50187?
To address CVE-2024-50187, update to the latest stable version of the Linux kernel which includes the relevant fixes.
What versions of the Linux kernel are affected by CVE-2024-50187?
CVE-2024-50187 affects Linux kernel versions between 4.17 and 6.1.113, and versions from 6.2 to 6.6.57, as well as the 6.12-rc1 and 6.12-rc2 releases.
What is the primary issue described in CVE-2024-50187?
The primary issue in CVE-2024-50187 is that the active performance monitor is not stopped when the file descriptor is closed, potentially leading to resource leaks.
Is there a workaround for CVE-2024-50187?
There are no specific workarounds for CVE-2024-50187; the best course of action is to apply the kernel updates that mitigate this vulnerability.