linux-cve-announce - CVE-2022-50615: perf/x86/intel/uncore: Fix reference count leak in snr_uncore_mmio

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: <2025120851-CVE-2022-50615-5c90@gregkh>
Date: Mon,  8 Dec 2025 10:16:52 +0900
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50615: perf/x86/intel/uncore: Fix reference count leak in snr_uncore_mmio_map()

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

perf/x86/intel/uncore: Fix reference count leak in snr_uncore_mmio_map()

pci_get_device() will increase the reference count for the returned
pci_dev, so snr_uncore_get_mc_dev() will return a pci_dev with its
reference count increased. We need to call pci_dev_put() to decrease the
reference count. Let's add the missing pci_dev_put().

The Linux kernel CVE team has assigned CVE-2022-50615 to this issue.


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

	Issue introduced in 5.3 with commit ee49532b38dd084650bf715eabe7e3828fb8d275 and fixed in 5.10.163 with commit d2afced51108813256d8072c6e464b0c9f0bb890
	Issue introduced in 5.3 with commit ee49532b38dd084650bf715eabe7e3828fb8d275 and fixed in 5.15.86 with commit 433bd587dca5c3f7157fef2fe571290cd392cbf6
	Issue introduced in 5.3 with commit ee49532b38dd084650bf715eabe7e3828fb8d275 and fixed in 6.0.16 with commit a67146437b6428069b71a7e5e740a2a8e1c40ac9
	Issue introduced in 5.3 with commit ee49532b38dd084650bf715eabe7e3828fb8d275 and fixed in 6.1.2 with commit dc7f07bc1ebb56a23fd1c4f664db5cbeb8900800
	Issue introduced in 5.3 with commit ee49532b38dd084650bf715eabe7e3828fb8d275 and fixed in 6.2 with commit 8ebd16c11c346751b3944d708e6c181ed4746c39

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-2022-50615
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:
	arch/x86/events/intel/uncore_snbep.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/d2afced51108813256d8072c6e464b0c9f0bb890
	https://git.kernel.org/stable/c/433bd587dca5c3f7157fef2fe571290cd392cbf6
	https://git.kernel.org/stable/c/a67146437b6428069b71a7e5e740a2a8e1c40ac9
	https://git.kernel.org/stable/c/dc7f07bc1ebb56a23fd1c4f664db5cbeb8900800
	https://git.kernel.org/stable/c/8ebd16c11c346751b3944d708e6c181ed4746c39