| 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: <2025022653-CVE-2022-49058-5df2@gregkh> Date: Wed, 26 Feb 2025 02:54:23 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: CVE-2022-49058: cifs: potential buffer overflow in handling symlinks Description =========== In the Linux kernel, the following vulnerability has been resolved: cifs: potential buffer overflow in handling symlinks Smatch printed a warning: arch/x86/crypto/poly1305_glue.c:198 poly1305_update_arch() error: __memcpy() 'dctx->buf' too small (16 vs u32max) It's caused because Smatch marks 'link_len' as untrusted since it comes from sscanf(). Add a check to ensure that 'link_len' is not larger than the size of the 'link_str' buffer. The Linux kernel CVE team has assigned CVE-2022-49058 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.37 with commit c69c1b6eaea1b3e1eecf7ad2fba0208ac4a11131 and fixed in 4.9.311 with commit 3e582749e742e662a8e9bb37cffac62dccaaa1e2 Issue introduced in 2.6.37 with commit c69c1b6eaea1b3e1eecf7ad2fba0208ac4a11131 and fixed in 4.14.276 with commit 1316c28569a80ab3596eeab05bf5e01991e7e739 Issue introduced in 2.6.37 with commit c69c1b6eaea1b3e1eecf7ad2fba0208ac4a11131 and fixed in 4.19.239 with commit eb5f51756944735ac70cd8bb38637cc202e29c91 Issue introduced in 2.6.37 with commit c69c1b6eaea1b3e1eecf7ad2fba0208ac4a11131 and fixed in 5.4.190 with commit 22d658c6c5affed10c8907e67160cef0b6c92186 Issue introduced in 2.6.37 with commit c69c1b6eaea1b3e1eecf7ad2fba0208ac4a11131 and fixed in 5.10.112 with commit 4e166a41180be2f1e66bbb6d46448e80a9a5ec05 Issue introduced in 2.6.37 with commit c69c1b6eaea1b3e1eecf7ad2fba0208ac4a11131 and fixed in 5.15.35 with commit 9901b07ba42b39266b34a888e48d7306fd707bee Issue introduced in 2.6.37 with commit c69c1b6eaea1b3e1eecf7ad2fba0208ac4a11131 and fixed in 5.17.4 with commit 515e7ba11ef043d6febe69389949c8ef5f25e9d0 Issue introduced in 2.6.37 with commit c69c1b6eaea1b3e1eecf7ad2fba0208ac4a11131 and fixed in 5.18 with commit 64c4a37ac04eeb43c42d272f6e6c8c12bfcf4304 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-49058 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: fs/cifs/link.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/3e582749e742e662a8e9bb37cffac62dccaaa1e2 https://git.kernel.org/stable/c/1316c28569a80ab3596eeab05bf5e01991e7e739 https://git.kernel.org/stable/c/eb5f51756944735ac70cd8bb38637cc202e29c91 https://git.kernel.org/stable/c/22d658c6c5affed10c8907e67160cef0b6c92186 https://git.kernel.org/stable/c/4e166a41180be2f1e66bbb6d46448e80a9a5ec05 https://git.kernel.org/stable/c/9901b07ba42b39266b34a888e48d7306fd707bee https://git.kernel.org/stable/c/515e7ba11ef043d6febe69389949c8ef5f25e9d0 https://git.kernel.org/stable/c/64c4a37ac04eeb43c42d272f6e6c8c12bfcf4304
Powered by blists - more mailing lists