# CVE-2024-50187: drm/vc4: Stop the active perfmon before being destroyed

> A use-after-free vulnerability in the Linux kernel's vc4 DRM driver allows attackers to cause denial of service or potentially execute code via stale pointers.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Nov 2024
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-53723, BELL-CVE-2024-50187, DEBIAN-CVE-2024-50187, GHSA-4p6c-9pp4-835h, ROOT-OS-DEBIAN-11-CVE-2024-50187, ROOT-OS-UBUNTU-2204-CVE-2024-50187, UBUNTU-CVE-2024-50187

## What is CVE-2024-50187?

CVE-2024-50187 is a high-severity use after free vulnerability in Linux kernel, published on 8 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2024-50187?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-50187?

Apply the vendor's patch.

## Is CVE-2024-50187 being exploited?

There is no known exploitation of CVE-2024-50187 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-50187 and fix it if it is affected.

What it is: CVE-2024-50187 is a high-severity use after free vulnerability in Linux kernel, published on 8 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-50187 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-50187/ (Markdown: https://insights.sbomify.com/CVE-2024-50187/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-50187
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-50187
- OSV: https://osv.dev/vulnerability/CVE-2024-50187

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-50187/
Summaries are generated and may contain mistakes; the official description above is the record.