Answer in brief
CVE-2024-50187 records a Unknown severity vulnerability in drm/vc4: Stop the active perfmon before being destroyed. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=65101d8c9108201118efa7e08f4e2c57f438deb9 <75452da51e2403e14be007df80d133e1443fc967 || >=65101d8c9108201118efa7e08f4e2c57f438deb9 <937943c042503dc6087438bf3557f9057a588ba0 || >=65101d8c9108201118efa7e08f4e2c57f438deb9 <c9adba739d5f7cdc47a7754df4a17b47b1ecf513 || >=65101d8c9108201118efa7e08f4e2c57f438deb9 <0b2ad4f6f2bec74a5287d96cb2325a5e11706f22 | 75452da51e2403e14be007df80d133e1443fc967, 937943c042503dc6087438bf3557f9057a588ba0, c9adba739d5f7cdc47a7754df4a17b47b1ecf513, 0b2ad4f6f2bec74a5287d96cb2325a5e11706f22 |
| Linux/Linuxgeneric | 4.17 | Not reported |
Published upstream
Nov 8, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-50187 records a Unknown severity vulnerability in drm/vc4: Stop the active perfmon before being destroyed. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=65101d8c9108201118efa7e08f4e2c57f438deb9 <75452da51e2403e14be007df80d133e1443fc967 || >=65101d8c9108201118efa7e08f4e2c57f438deb9 <937943c042503dc6087438bf3557f9057a588ba0 || >=65101d8c9108201118efa7e08f4e2c57f438deb9 <c9adba739d5f7cdc47a7754df4a17b47b1ecf513 || >=65101d8c9108201118efa7e08f4e2c57f438deb9 <0b2ad4f6f2bec74a5287d96cb2325a5e11706f22 | 75452da51e2403e14be007df80d133e1443fc967, 937943c042503dc6087438bf3557f9057a588ba0, c9adba739d5f7cdc47a7754df4a17b47b1ecf513, 0b2ad4f6f2bec74a5287d96cb2325a5e11706f22 |
| Linux/Linuxgeneric | 4.17 | Not reported |
Published upstream
Nov 8, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.