| 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
| ||
|
Message-ID: <2025100422-CVE-2022-50505-b427@gregkh> Date: Sat, 4 Oct 2025 17:51:30 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2022-50505: iommu/amd: Fix pci device refcount leak in ppr_notifier() From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Fix pci device refcount leak in ppr_notifier() As comment of pci_get_domain_bus_and_slot() says, it returns a pci device with refcount increment, when finish using it, the caller must decrement the reference count by calling pci_dev_put(). So call it before returning from ppr_notifier() to avoid refcount leak. The Linux kernel CVE team has assigned CVE-2022-50505 to this issue. Affected and fixed versions =========================== Issue introduced in 4.14 with commit daae2d25a4779b272a66ddd01f5810bcee822b9e and fixed in 4.14.303 with commit bdb2113dd8f17a3cc84a2b4be4968a849f69ec72 Issue introduced in 4.14 with commit daae2d25a4779b272a66ddd01f5810bcee822b9e and fixed in 4.19.270 with commit efd50c65fd1cdef63eb58825f3fe72496443764c Issue introduced in 4.14 with commit daae2d25a4779b272a66ddd01f5810bcee822b9e and fixed in 5.4.229 with commit 8581ec1feb895ff596fe3d326d9ba320083290aa Issue introduced in 4.14 with commit daae2d25a4779b272a66ddd01f5810bcee822b9e and fixed in 5.10.163 with commit 03f51c72997559e73b327608f0cccfded715c9a0 Issue introduced in 4.14 with commit daae2d25a4779b272a66ddd01f5810bcee822b9e and fixed in 5.15.86 with commit 6e501b3fd7a2e1c4372d72bc70717aaca2beb8a5 Issue introduced in 4.14 with commit daae2d25a4779b272a66ddd01f5810bcee822b9e and fixed in 6.0.16 with commit 902cc2507091a81643502d8ceb0e2f105e902518 Issue introduced in 4.14 with commit daae2d25a4779b272a66ddd01f5810bcee822b9e and fixed in 6.1.2 with commit b0637f4bd426925f5c3a15e8f8e36190fe06bac5 Issue introduced in 4.14 with commit daae2d25a4779b272a66ddd01f5810bcee822b9e and fixed in 6.2 with commit 6cf0981c2233f97d56938d9d61845383d6eb227c 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-50505 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/iommu/amd/iommu_v2.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/bdb2113dd8f17a3cc84a2b4be4968a849f69ec72 https://git.kernel.org/stable/c/efd50c65fd1cdef63eb58825f3fe72496443764c https://git.kernel.org/stable/c/8581ec1feb895ff596fe3d326d9ba320083290aa https://git.kernel.org/stable/c/03f51c72997559e73b327608f0cccfded715c9a0 https://git.kernel.org/stable/c/6e501b3fd7a2e1c4372d72bc70717aaca2beb8a5 https://git.kernel.org/stable/c/902cc2507091a81643502d8ceb0e2f105e902518 https://git.kernel.org/stable/c/b0637f4bd426925f5c3a15e8f8e36190fe06bac5 https://git.kernel.org/stable/c/6cf0981c2233f97d56938d9d61845383d6eb227c
Powered by blists - more mailing lists