From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 8DC1BE567 for ; Thu, 1 May 2025 14:13:00 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1746108780; cv=none; b=YK+7cTKSrcFe7GgZpi9fw7grkwwqbacnAScC6+8gTM1Z+uRxyYrf9Hw0Yr1GfmiqtwWX0PIharXmFXpSLisXJ2zpawWl9xigCdlXWud6UGiVxKgqLrS8ucCwGumlkxOB0M1EYWQvQluqUCAg5D6Cd18qF4r50l16PCiw/P7Z4ts= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1746108780; c=relaxed/simple; bh=CpXui2ll6s5irSVtET5g6b6IE2zdI+cHeWS0w5/Ku0U=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=hVwcQTTctX1X4cAtNrHudj+sWuImAxsI+97N5Ofw/r/KkPCR/i/ZUb7hd8S8BOFzqANQz8o5yHleEUn3+AAmgRuU/pLiIoad33V4Mgh4CN4e7Sx73lFbyuIqIAhmvAhqyyWXU9hc8tXAkyOlKPV6xU1ACkdKwOgu7ecDo83YAHM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=wqQeoJxx; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="wqQeoJxx" Received: by smtp.kernel.org (Postfix) with ESMTPSA id EE616C4CEE3; Thu, 1 May 2025 14:12:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1746108780; bh=CpXui2ll6s5irSVtET5g6b6IE2zdI+cHeWS0w5/Ku0U=; h=From:To:Cc:Subject:Date:Reply-to:From; b=wqQeoJxxsly+QfydwSR2//sIBCMZfKEWqcKYR/Nxbu6DBYUL0MdvrpamuMEvKhlfi eYDbbzWyqxs7hSP/2p0MeU0jdnzWxCwFas4ZMxLkIuOh/VJmt9va+AG8fmWV8YwJvT 7iNLS/Gqwuk+JP2baC/2vfs8YVobL6wZ5iNyE9E0= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2022-49780: scsi: target: tcm_loop: Fix possible name leak in tcm_loop_setup_hba_bus() Date: Thu, 1 May 2025 16:09:30 +0200 Message-ID: <2025050119-CVE-2022-49780-e1de@gregkh> X-Mailer: git-send-email 2.49.0 Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Reply-to: , X-Developer-Signature: v=1; a=openpgp-sha256; l=3134; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=MQguQW69iQmT+FMP9dJ4jlB5YlKQoJ1yY8DWGAajo1w=; b=owGbwMvMwCRo6H6F97bub03G02pJDBnCDf0a7gp/rYMua6daLvaM0j6peWH7hl/vN5d0RIvEd UzPyd7dEcvCIMjEICumyPJlG8/R/RWHFL0MbU/DzGFlAhnCwMUpABO5fYZhwVSWu34L7rLr/q36 pR7ltPzGA1a2IIYFh2J/Ht716PLTvKoZeu+lbk4wDbTgAwA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: scsi: target: tcm_loop: Fix possible name leak in tcm_loop_setup_hba_bus() If device_register() fails in tcm_loop_setup_hba_bus(), the name allocated by dev_set_name() need be freed. As comment of device_register() says, it should use put_device() to give up the reference in the error path. So fix this by calling put_device(), then the name can be freed in kobject_cleanup(). The 'tl_hba' will be freed in tcm_loop_release_adapter(), so it don't need goto error label in this case. The Linux kernel CVE team has assigned CVE-2022-49780 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.39 with commit 3703b2c5d041a68095cdd22380c23ce27d449ad7 and fixed in 4.19.267 with commit 41a6b8b527a5957fab41c3c05e25ad125268e2e9 Issue introduced in 2.6.39 with commit 3703b2c5d041a68095cdd22380c23ce27d449ad7 and fixed in 5.4.225 with commit 28f7ff5e7559d226e63c7c5de74eb075a83d8c53 Issue introduced in 2.6.39 with commit 3703b2c5d041a68095cdd22380c23ce27d449ad7 and fixed in 5.10.156 with commit 75205f1b47a88c3fac4f30bd7567e89b2887c7fd Issue introduced in 2.6.39 with commit 3703b2c5d041a68095cdd22380c23ce27d449ad7 and fixed in 5.15.80 with commit a636772988bafab89278e7bb3420d8e8eacfe912 Issue introduced in 2.6.39 with commit 3703b2c5d041a68095cdd22380c23ce27d449ad7 and fixed in 6.0.10 with commit dce0589a3faec9e2e543e97bca7e62592ec85585 Issue introduced in 2.6.39 with commit 3703b2c5d041a68095cdd22380c23ce27d449ad7 and fixed in 6.1 with commit bc68e428d4963af0201e92159629ab96948f0893 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-49780 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/target/loopback/tcm_loop.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/41a6b8b527a5957fab41c3c05e25ad125268e2e9 https://git.kernel.org/stable/c/28f7ff5e7559d226e63c7c5de74eb075a83d8c53 https://git.kernel.org/stable/c/75205f1b47a88c3fac4f30bd7567e89b2887c7fd https://git.kernel.org/stable/c/a636772988bafab89278e7bb3420d8e8eacfe912 https://git.kernel.org/stable/c/dce0589a3faec9e2e543e97bca7e62592ec85585 https://git.kernel.org/stable/c/bc68e428d4963af0201e92159629ab96948f0893