| 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: <2025091552-CVE-2022-50318-6f5e@gregkh> Date: Mon, 15 Sep 2025 16:48:55 +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-50318: perf/x86/intel/uncore: Fix reference count leak in hswep_has_limit_sbox() 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 hswep_has_limit_sbox() pci_get_device() will increase the reference count for the returned 'dev'. We need to call pci_dev_put() to decrease the reference count. Since 'dev' is only used in pci_read_config_dword(), let's add pci_dev_put() right after it. The Linux kernel CVE team has assigned CVE-2022-50318 to this issue. Affected and fixed versions =========================== Issue introduced in 4.19.189 with commit a8e87042482fd2d31c5cee62875b2ae75759ae8b and fixed in 4.19.270 with commit 5a96c10a56037db006ba6769307a9731cf6073be Issue introduced in 5.4.115 with commit 319a06e58ed7f1443f7133c05513de470f90628d and fixed in 5.4.229 with commit e293263248f25c6b8aa1caf7c1103d40aa03311e Issue introduced in 5.10.33 with commit 6f8315e5d9511ed1cf28ee2afbc9f89ff693de7b and fixed in 5.10.163 with commit c0539d5d474ee6fa4ebc41f927a0f98f81244f25 Issue introduced in 5.12 with commit 9d480158ee86ad606d3a8baaf81e6b71acbfd7d5 and fixed in 5.15.86 with commit 3485f197518061371568f842405159aa9e4df551 Issue introduced in 5.12 with commit 9d480158ee86ad606d3a8baaf81e6b71acbfd7d5 and fixed in 6.0.16 with commit 48f32b9a74e2ac8e854bb87bfefdbc745125a123 Issue introduced in 5.12 with commit 9d480158ee86ad606d3a8baaf81e6b71acbfd7d5 and fixed in 6.1.2 with commit bd66877c0b3b42eed0ecee0bd2a2a505c1e54177 Issue introduced in 5.12 with commit 9d480158ee86ad606d3a8baaf81e6b71acbfd7d5 and fixed in 6.2 with commit 1ff9dd6e7071a561f803135c1d684b13c7a7d01d Issue introduced in 5.11.17 with commit d2c79105a90323a2a93484c85f9ac419ae9b183d 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-50318 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/5a96c10a56037db006ba6769307a9731cf6073be https://git.kernel.org/stable/c/e293263248f25c6b8aa1caf7c1103d40aa03311e https://git.kernel.org/stable/c/c0539d5d474ee6fa4ebc41f927a0f98f81244f25 https://git.kernel.org/stable/c/3485f197518061371568f842405159aa9e4df551 https://git.kernel.org/stable/c/48f32b9a74e2ac8e854bb87bfefdbc745125a123 https://git.kernel.org/stable/c/bd66877c0b3b42eed0ecee0bd2a2a505c1e54177 https://git.kernel.org/stable/c/1ff9dd6e7071a561f803135c1d684b13c7a7d01d
Powered by blists - more mailing lists