From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
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 [thread overview]
Message-ID: <2025050119-CVE-2022-49780-e1de@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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
reply other threads:[~2025-05-01 14:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025050119-CVE-2022-49780-e1de@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.