| 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: <2025100704-CVE-2022-50521-fd26@gregkh> Date: Tue, 7 Oct 2025 17:19:08 +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-50521: platform/x86: mxm-wmi: fix memleak in mxm_wmi_call_mx[ds|mx]() From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: platform/x86: mxm-wmi: fix memleak in mxm_wmi_call_mx[ds|mx]() The ACPI buffer memory (out.pointer) returned by wmi_evaluate_method() is not freed after the call, so it leads to memory leak. The method results in ACPI buffer is not used, so just pass NULL to wmi_evaluate_method() which fixes the memory leak. The Linux kernel CVE team has assigned CVE-2022-50521 to this issue. Affected and fixed versions =========================== Issue introduced in 3.0 with commit 99b38b4acc0d7dbbab443273577cff60080fcfad and fixed in 4.14.303 with commit 50ac517d6f5348b276f1f663799cf85dce521518 Issue introduced in 3.0 with commit 99b38b4acc0d7dbbab443273577cff60080fcfad and fixed in 4.19.270 with commit 5b0f81b0808235967868e01336c976e840217108 Issue introduced in 3.0 with commit 99b38b4acc0d7dbbab443273577cff60080fcfad and fixed in 5.4.229 with commit 14bb4bde3b7b2584734b13747b345caeeb41bea3 Issue introduced in 3.0 with commit 99b38b4acc0d7dbbab443273577cff60080fcfad and fixed in 5.10.163 with commit 17cd8c46cbec4e6ad593fb9159928b8e7608c11a Issue introduced in 3.0 with commit 99b38b4acc0d7dbbab443273577cff60080fcfad and fixed in 5.15.86 with commit 3cf81501356c9e898ad94b2369ffc805f83f7d7b Issue introduced in 3.0 with commit 99b38b4acc0d7dbbab443273577cff60080fcfad and fixed in 6.0.16 with commit 379e7794c5e7485193d25d73614fbbd1e1387f6f Issue introduced in 3.0 with commit 99b38b4acc0d7dbbab443273577cff60080fcfad and fixed in 6.1.2 with commit 87426ce3bd57ad414b6e2436434ef8128986a9a5 Issue introduced in 3.0 with commit 99b38b4acc0d7dbbab443273577cff60080fcfad and fixed in 6.2 with commit 727cc0147f5066e359aca65cc6cc5e6d64cc15d8 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-50521 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/platform/x86/mxm-wmi.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/50ac517d6f5348b276f1f663799cf85dce521518 https://git.kernel.org/stable/c/5b0f81b0808235967868e01336c976e840217108 https://git.kernel.org/stable/c/14bb4bde3b7b2584734b13747b345caeeb41bea3 https://git.kernel.org/stable/c/17cd8c46cbec4e6ad593fb9159928b8e7608c11a https://git.kernel.org/stable/c/3cf81501356c9e898ad94b2369ffc805f83f7d7b https://git.kernel.org/stable/c/379e7794c5e7485193d25d73614fbbd1e1387f6f https://git.kernel.org/stable/c/87426ce3bd57ad414b6e2436434ef8128986a9a5 https://git.kernel.org/stable/c/727cc0147f5066e359aca65cc6cc5e6d64cc15d8
Powered by blists - more mailing lists