| 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: <2025061818-CVE-2022-50140-cb08@gregkh> Date: Wed, 18 Jun 2025 13:03:25 +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-50140: memstick/ms_block: Fix a memory leak From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: memstick/ms_block: Fix a memory leak 'erased_blocks_bitmap' is never freed. As it is allocated at the same time as 'used_blocks_bitmap', it is likely that it should be freed also at the same time. Add the corresponding bitmap_free() in msb_data_clear(). The Linux kernel CVE team has assigned CVE-2022-50140 to this issue. Affected and fixed versions =========================== Issue introduced in 3.12 with commit 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 and fixed in 4.14.291 with commit efd675246aec045507b9425c67b548cc2d782d8f Issue introduced in 3.12 with commit 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 and fixed in 4.19.256 with commit 37958980eb4cd71ae594ace093c11b6a91e165e8 Issue introduced in 3.12 with commit 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 and fixed in 5.4.211 with commit 9d8b911fe3c3ed788c66edba7c90e32a4a7a5f53 Issue introduced in 3.12 with commit 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 and fixed in 5.10.137 with commit 9260a154b3b5e387dbceec7c0ac441470646bc6f Issue introduced in 3.12 with commit 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 and fixed in 5.15.61 with commit 961d7d12080fe70847f944d656e36cd0dd0214ba Issue introduced in 3.12 with commit 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 and fixed in 5.18.18 with commit 16e07966638717416abf45393d6a80a5a1034429 Issue introduced in 3.12 with commit 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 and fixed in 5.19.2 with commit 39be95d1ff7b44c1e969af72ba9da7332dfcc1da Issue introduced in 3.12 with commit 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 and fixed in 6.0 with commit 54eb7a55be6779c4d0c25eaf5056498a28595049 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-50140 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/memstick/core/ms_block.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/efd675246aec045507b9425c67b548cc2d782d8f https://git.kernel.org/stable/c/37958980eb4cd71ae594ace093c11b6a91e165e8 https://git.kernel.org/stable/c/9d8b911fe3c3ed788c66edba7c90e32a4a7a5f53 https://git.kernel.org/stable/c/9260a154b3b5e387dbceec7c0ac441470646bc6f https://git.kernel.org/stable/c/961d7d12080fe70847f944d656e36cd0dd0214ba https://git.kernel.org/stable/c/16e07966638717416abf45393d6a80a5a1034429 https://git.kernel.org/stable/c/39be95d1ff7b44c1e969af72ba9da7332dfcc1da https://git.kernel.org/stable/c/54eb7a55be6779c4d0c25eaf5056498a28595049
Powered by blists - more mailing lists