CVE-2024-50187

published 8 Nov 2024 · updated 12 Aug 2026

drm/vc4: Stop the active perfmon before being destroyed

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0b2ad4f6f2bec74a5287d96cb2325a5e11706f22, Kernel 75452da51e2403e14be007df80d133e1443fc967, Kernel 937943c042503dc6087438bf3557f9057a588ba0 and 1 more.

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 `vc4_perfmon_close_file()`, the active performance monitor's pointer (`vc4->active_perfmon`) 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->active_perfmon`. 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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=4.17, >=65101d8c9108201118efa7e08f4e2c57f438deb9 <0b2ad4f6f2bec74a5287d96cb2325a5e11706f22, >=65101d8c9108201118efa7e08f4e2c57f438deb9 <75452da51e2403e14be007df80d133e1443fc967, >=65101d8c9108201118efa7e08f4e2c57f438deb9 <937943c042503dc6087438bf3557f9057a588ba0, >=65101d8c9108201118efa7e08f4e2c57f438deb9 <c9adba739d5f7cdc47a7754df4a17b47b1ecf5130b2ad4f6f2bec74a5287d96cb2325a5e11706f22, 75452da51e2403e14be007df80d133e1443fc967, 937943c042503dc6087438bf3557f9057a588ba0, c9adba739d5f7cdc47a7754df4a17b47b1ecf513

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2024-50187 severity on Zeptric[![CVE-2024-50187](https://zeptric.io/badge/cve/CVE-2024-50187.svg)](https://zeptric.io/cve/CVE-2024-50187)