CVE-2024-50187
Last modified
CVE-2024-50187 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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`. EPSS estimates a 0.22% chance of exploitation in the next 30 days.
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.
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 | >= 4.17, < 6.1.113 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.57 | — |
| Linux | Linux Kernel | >= 6.7, < 6.11.4 | — |
| Linux | Linux Kernel | 6.12 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-50187?
How severe is CVE-2024-50187?
How do I fix CVE-2024-50187?
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-50181Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2024-50182In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50183In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2024-50184In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50185In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50186In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-50188In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50189In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-5019In WhatsUp Gold versions released before 2023.1.3, an unau…7.5
- CVE-2024-50190In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50191In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-50192In the Linux kernel, the following vulnerability has been re…4.7
Are you affected by CVE-2024-50187?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST