linux-cve-announce - CVE-2024-50187: drm/vc4: Stop the active perfmon before being destroyed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2024110835-CVE-2024-50187-f2b0@gregkh>
Date: Fri,  8 Nov 2024 06:38:40 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-50187: drm/vc4: Stop the active perfmon before being destroyed

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.

The Linux kernel CVE team has assigned CVE-2024-50187 to this issue.

Affected and fixed versions
===========================

	Issue introduced in 4.17 with commit 65101d8c9108 and fixed in 6.1.113 with commit 75452da51e24
	Issue introduced in 4.17 with commit 65101d8c9108 and fixed in 6.6.57 with commit 937943c04250
	Issue introduced in 4.17 with commit 65101d8c9108 and fixed in 6.11.4 with commit c9adba739d5f
	Issue introduced in 4.17 with commit 65101d8c9108 and fixed in 6.12-rc3 with commit 0b2ad4f6f2be

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2024-50187
will be updated if fixes are backported, please check that for the most
up to date information about this issue.

Affected files
==============

The file(s) affected by this issue are:
	drivers/gpu/drm/vc4/vc4_perfmon.c

Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/75452da51e2403e14be007df80d133e1443fc967
	https://git.kernel.org/stable/c/937943c042503dc6087438bf3557f9057a588ba0
	https://git.kernel.org/stable/c/c9adba739d5f7cdc47a7754df4a17b47b1ecf513
	https://git.kernel.org/stable/c/0b2ad4f6f2bec74a5287d96cb2325a5e11706f22