| 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: <2025061828-CVE-2022-50169-540a@gregkh> Date: Wed, 18 Jun 2025 13:03:54 +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-50169: wifi: wil6210: debugfs: fix info leak in wil_write_file_wmi() From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: wifi: wil6210: debugfs: fix info leak in wil_write_file_wmi() The simple_write_to_buffer() function will succeed if even a single byte is initialized. However, we need to initialize the whole buffer to prevent information leaks. Just use memdup_user(). The Linux kernel CVE team has assigned CVE-2022-50169 to this issue. Affected and fixed versions =========================== Issue introduced in 3.17 with commit ff974e4083341383d3dd4079e52ed30f57f376f0 and fixed in 4.14.291 with commit c1216e699a1ce83ea005510844bd7508d34c6cef Issue introduced in 3.17 with commit ff974e4083341383d3dd4079e52ed30f57f376f0 and fixed in 4.19.256 with commit 4615458db7793fadc6d546ac3564b36819e77a22 Issue introduced in 3.17 with commit ff974e4083341383d3dd4079e52ed30f57f376f0 and fixed in 5.4.211 with commit 60c9983425167ec5073c628d83a6875760d18059 Issue introduced in 3.17 with commit ff974e4083341383d3dd4079e52ed30f57f376f0 and fixed in 5.10.137 with commit 05ceda14ef7c73104e709c414c3680d8a59f51d4 Issue introduced in 3.17 with commit ff974e4083341383d3dd4079e52ed30f57f376f0 and fixed in 5.15.61 with commit 074e865b37da55aa87baa16d68b96896f85f8adb Issue introduced in 3.17 with commit ff974e4083341383d3dd4079e52ed30f57f376f0 and fixed in 5.18.18 with commit 789edc1af9c1a2293956e8534bfef3d18d629de9 Issue introduced in 3.17 with commit ff974e4083341383d3dd4079e52ed30f57f376f0 and fixed in 5.19.2 with commit 67470920cd3f3cb38699b1ad23234f96bead4d21 Issue introduced in 3.17 with commit ff974e4083341383d3dd4079e52ed30f57f376f0 and fixed in 6.0 with commit 7a4836560a6198d245d5732e26f94898b12eb760 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-50169 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/net/wireless/ath/wil6210/debugfs.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/c1216e699a1ce83ea005510844bd7508d34c6cef https://git.kernel.org/stable/c/4615458db7793fadc6d546ac3564b36819e77a22 https://git.kernel.org/stable/c/60c9983425167ec5073c628d83a6875760d18059 https://git.kernel.org/stable/c/05ceda14ef7c73104e709c414c3680d8a59f51d4 https://git.kernel.org/stable/c/074e865b37da55aa87baa16d68b96896f85f8adb https://git.kernel.org/stable/c/789edc1af9c1a2293956e8534bfef3d18d629de9 https://git.kernel.org/stable/c/67470920cd3f3cb38699b1ad23234f96bead4d21 https://git.kernel.org/stable/c/7a4836560a6198d245d5732e26f94898b12eb760
Powered by blists - more mailing lists