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: <2025011532-CVE-2024-53681-e199@gregkh> Date: Wed, 15 Jan 2025 14:10:34 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: CVE-2024-53681: nvmet: Don't overflow subsysnqn Description =========== In the Linux kernel, the following vulnerability has been resolved: nvmet: Don't overflow subsysnqn nvmet_root_discovery_nqn_store treats the subsysnqn string like a fixed size buffer, even though it is dynamically allocated to the size of the string. Create a new string with kstrndup instead of using the old buffer. The Linux kernel CVE team has assigned CVE-2024-53681 to this issue. Affected and fixed versions =========================== Issue introduced in 6.9 with commit 95409e277d8343810adf8700d29d4329828d452b and fixed in 6.12.9 with commit 86645d8d062af3fdcbdaa0a289b95de55bca827d Issue introduced in 6.9 with commit 95409e277d8343810adf8700d29d4329828d452b and fixed in 6.13-rc6 with commit 4db3d750ac7e894278ef1cb1c53cc7d883060496 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-2024-53681 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/nvme/target/configfs.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/86645d8d062af3fdcbdaa0a289b95de55bca827d https://git.kernel.org/stable/c/4db3d750ac7e894278ef1cb1c53cc7d883060496
Powered by blists - more mailing lists