CVE-2022-49780
published 2025-05-01CVE-2022-49780: 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…
PriorityP416medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.21%
10.7th percentile
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.
Affected
18 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.0.10-1 (bookworm) | linux 6.0.10-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 3703b2c5d041a68095cdd22380c23ce27d449ad7 < 41a6b8b527a5957fab41c3c05e25ad125268e2e9 | 41a6b8b527a5957fab41c3c05e25ad125268e2e9 |
| linux | linux | >= 3703b2c5d041a68095cdd22380c23ce27d449ad7 < 28f7ff5e7559d226e63c7c5de74eb075a83d8c53 | 28f7ff5e7559d226e63c7c5de74eb075a83d8c53 |
| linux | linux | >= 3703b2c5d041a68095cdd22380c23ce27d449ad7 < 75205f1b47a88c3fac4f30bd7567e89b2887c7fd | 75205f1b47a88c3fac4f30bd7567e89b2887c7fd |
| linux | linux | >= 3703b2c5d041a68095cdd22380c23ce27d449ad7 < a636772988bafab89278e7bb3420d8e8eacfe912 | a636772988bafab89278e7bb3420d8e8eacfe912 |
| linux | linux | >= 3703b2c5d041a68095cdd22380c23ce27d449ad7 < dce0589a3faec9e2e543e97bca7e62592ec85585 | dce0589a3faec9e2e543e97bca7e62592ec85585 |
| linux | linux | >= 3703b2c5d041a68095cdd22380c23ce27d449ad7 < bc68e428d4963af0201e92159629ab96948f0893 | bc68e428d4963af0201e92159629ab96948f0893 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.158-1 | 5.10.158-1 |
| linux | linux_kernel | >= 0 < 6.0.10-1 | 6.0.10-1 |
| linux | linux_kernel | >= 0 < 6.0.10-1 | 6.0.10-1 |
| linux | linux_kernel | >= 0 < 6.0.10-1 | 6.0.10-1 |
| linux | linux_kernel | >= 2.6.39 < 4.19.267 | 4.19.267 |
| linux | linux_kernel | >= 4.20 < 5.4.225 | 5.4.225 |
| linux | linux_kernel | >= 5.11 < 5.15.80 | 5.15.80 |
| linux | linux_kernel | >= 5.16 < 6.0.10 | 6.0.10 |
| linux | linux_kernel | >= 5.5 < 5.10.156 | 5.10.156 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-px2q-r9rv-q5m3: 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 de
ghsa_unreviewed·2025-05-01
CVE-2022-49780 [MEDIUM] CWE-401 GHSA-px2q-r9rv-q5m3: 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 de
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.
OSV
CVE-2022-49780: 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 devi
osv·2025-05-01·CVSS 5.5
CVE-2022-49780 [MEDIUM] CVE-2022-49780: 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 devi
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.
Red Hat
kernel: scsi: target: tcm_loop: Fix possible name leak in tcm_loop_setup_hba_bus()
vendor_redhat·2025-05-01·CVSS 5.5
CVE-2022-49780 [MEDIUM] kernel: scsi: target: tcm_loop: Fix possible name leak in tcm_loop_setup_hba_bus()
kernel: scsi: target: tcm_loop: Fix possible name leak in tcm_loop_setup_hba_bus()
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.
Statement: A memory leak was identified in tcm_loop_setup_hba_bus() where the name allocated via dev_set_name() was not released when device_register() failed. The
Debian
CVE-2022-49780: linux - In the Linux kernel, the following vulnerability has been resolved: scsi: targe...
vendor_debian·2022·CVSS 5.5
CVE-2022-49780 [MEDIUM] CVE-2022-49780: linux - In the Linux kernel, the following vulnerability has been resolved: scsi: targe...
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.
Scope: local
bookworm: resolved (fixed in 6.0.10-1)
bullseye: resolved (fixed in 5.10.158-1)
forky: resolved (fixed in 6.0.10-1)
sid: resolved (fixed in 6.0.10-1)
trixie: resolved (fixed in 6.0.10-1)
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/28f7ff5e7559d226e63c7c5de74eb075a83d8c53https://git.kernel.org/stable/c/41a6b8b527a5957fab41c3c05e25ad125268e2e9https://git.kernel.org/stable/c/75205f1b47a88c3fac4f30bd7567e89b2887c7fdhttps://git.kernel.org/stable/c/a636772988bafab89278e7bb3420d8e8eacfe912https://git.kernel.org/stable/c/bc68e428d4963af0201e92159629ab96948f0893https://git.kernel.org/stable/c/dce0589a3faec9e2e543e97bca7e62592ec85585
2025-05-01
Published