CVE-2024-50187
Severity CVSS v4.0:
Pending analysis
Type:
Unavailable / Other
Publication date:
08/11/2024
Last modified:
03/11/2025
Description
In the Linux kernel, the following vulnerability has been resolved:<br />
<br />
drm/vc4: Stop the active perfmon before being destroyed<br />
<br />
Upon closing the file descriptor, the active performance monitor is not<br />
stopped. Although all perfmons are destroyed in `vc4_perfmon_close_file()`,<br />
the active performance monitor&#39;s pointer (`vc4->active_perfmon`) is still<br />
retained.<br />
<br />
If we open a new file descriptor and submit a few jobs with performance<br />
monitors, the driver will attempt to stop the active performance monitor<br />
using the stale pointer in `vc4->active_perfmon`. However, this pointer<br />
is no longer valid because the previous process has already terminated,<br />
and all performance monitors associated with it have been destroyed and<br />
freed.<br />
<br />
To fix this, when the active performance monitor belongs to a given<br />
process, explicitly stop it before destroying and freeing it.
Impact
Base Score 3.x
5.50
Severity 3.x
MEDIUM
Vulnerable products and versions
| CPE | From | Up to |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | 4.17 (including) | 6.1.113 (excluding) |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | 6.2 (including) | 6.6.57 (excluding) |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | 6.7 (including) | 6.11.4 (excluding) |
| cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:* | ||
| cpe:2.3:o:linux:linux_kernel:6.12:rc2:*:*:*:*:*:* |
To consult the complete list of CPE names with products and versions, see this page
References to Advisories, Solutions, and Tools
- https://git.kernel.org/stable/c/0b2ad4f6f2bec74a5287d96cb2325a5e11706f22
- https://git.kernel.org/stable/c/75452da51e2403e14be007df80d133e1443fc967
- https://git.kernel.org/stable/c/937943c042503dc6087438bf3557f9057a588ba0
- https://git.kernel.org/stable/c/c9adba739d5f7cdc47a7754df4a17b47b1ecf513
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html



