blob: 21bee4236d602007c2770edcb3ee3548484080b9 [file] [log] [blame]
From bippy-1.2.0 Mon Sep 17 00:00:00 2001
From: Greg Kroah-Hartman <gregkh@kernel.org>
To: <linux-cve-announce@vger.kernel.org>
Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: CVE-2025-37746: perf/dwc_pcie: fix duplicate pci_dev devices
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
perf/dwc_pcie: fix duplicate pci_dev devices
During platform_device_register, wrongly using struct device
pci_dev as platform_data caused a kmemdup copy of pci_dev. Worse
still, accessing the duplicated device leads to list corruption as its
mutex content (e.g., list, magic) remains the same as the original.
The Linux kernel CVE team has assigned CVE-2025-37746 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.8 with commit af9597adc2f1e3609c67c9792a2469bb64e43ae9 and fixed in 6.14.3 with commit a71c6fc87b2b9905dc2e38887fe4122287216be9
Issue introduced in 6.8 with commit af9597adc2f1e3609c67c9792a2469bb64e43ae9 and fixed in 6.15 with commit 7f35b429802a8065aa61e2a3f567089649f4d98e
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-2025-37746
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/perf/dwc_pcie_pmu.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/a71c6fc87b2b9905dc2e38887fe4122287216be9
https://git.kernel.org/stable/c/7f35b429802a8065aa61e2a3f567089649f4d98e