CVE-2024-50187

GPU service interruption via stale perfmon pointer

Published Nov 8, 2024 · Updated Aug 5, 2026

Use-after-free in Linux 4.17 through 6.12-rc2 allows local users to interrupt GPU services through crafted VC4 performance-monitor jobs. vc4_perfmon_close_file() frees all monitors for a closing descriptor but leaves vc4->active_perfmon pointing to the freed active object, which later submissions dereference. Access to the VC4 DRM render node is required; exploitation can wedge performance monitoring or trigger a kernel panic on panic_on_warn systems.

CVSS severity5.5
Medium
EPSS probability0.23%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Use-after-free in Linux 4.17 through 6.12-rc2 allows local users to interrupt GPU services through crafted VC4 performance-monitor jobs. vc4_perfmon_close_file() frees all monitors for a closing descriptor but leaves vc4->active_perfmon pointing to the freed active object, which later submissions dereference. Access to the VC4 DRM render node is required; exploitation can wedge performance monitoring or trigger a kernel panic on panic_on_warn systems.

The record

CVE
CVE-2024-50187
Published
Nov 8, 2024
Updated
Aug 5, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
CWE-416, T1499
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Nov 8, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 5, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=4.17
  2. Affected versionversion=65101d8c9108201118efa7e08f4e2c57f438deb9 <0b2ad4f6f2bec74a5287d96cb2325a5e11706f22
  3. Affected versionversion=65101d8c9108201118efa7e08f4e2c57f438deb9 <75452da51e2403e14be007df80d133e1443fc967
  4. Affected versionversion=65101d8c9108201118efa7e08f4e2c57f438deb9 <937943c042503dc6087438bf3557f9057a588ba0
  5. Affected versionversion=65101d8c9108201118efa7e08f4e2c57f438deb9 <c9adba739d5f7cdc47a7754df4a17b47b1ecf513

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=4.17; version=65101d8c9108201118efa7e08f4e2c57f438deb9 <0b2ad4f6f2bec74a5287d96cb2325a5e11706f22; version=65101d8c9108201118efa7e08f4e2c57f438deb9 <75452da51e2403e14be007df80d133e1443fc967; version=65101d8c9108201118efa7e08f4e2c57f438deb9 <937943c042503dc6087438bf3557f9057a588ba0; version=65101d8c9108201118efa7e08f4e2c57f438deb9 <c9adba739d5f7cdc47a7754df4a17b47b1ecf513

Published CVSS scores

5.5SUSECVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
5.5NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
5.5UbuntuCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-416Use After Free
T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo