CVE-2022-49780
scsi: target: tcm_loop: Fix possible name leak in tcm_loop_setup_hba_bus()
- Published
- Updated
- Reserved
- Assigned by
- Linux
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.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.22% · top 88% of all CVEs (7 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Weakness
Affected products
- affected 3703b2c5d041a68095cdd22380c23ce27d449ad7 – < 41a6b8b527a5957fab41c3c05e25ad125268e2e9
- affected 3703b2c5d041a68095cdd22380c23ce27d449ad7 – < 28f7ff5e7559d226e63c7c5de74eb075a83d8c53
- affected 3703b2c5d041a68095cdd22380c23ce27d449ad7 – < 75205f1b47a88c3fac4f30bd7567e89b2887c7fd
- affected 3703b2c5d041a68095cdd22380c23ce27d449ad7 – < a636772988bafab89278e7bb3420d8e8eacfe912
- affected 3703b2c5d041a68095cdd22380c23ce27d449ad7 – < dce0589a3faec9e2e543e97bca7e62592ec85585
- affected 3703b2c5d041a68095cdd22380c23ce27d449ad7 – < bc68e428d4963af0201e92159629ab96948f0893
- affected 2.6.39
- unaffected < 2.6.39
- unaffected 4.19.267 – ≤ 4.19.*
- unaffected 5.4.225 – ≤ 5.4.*
- unaffected 5.10.156 – ≤ 5.10.*
- unaffected 5.15.80 – ≤ 5.15.*
- unaffected 6.0.10 – ≤ 6.0.*
- unaffected 6.1 – ≤ *
References (6)
- https://git.kernel.org/stable/c/41a6b8b527a5957fab41c3c05e25ad125268e2e9 (opens in a new tab)
- https://git.kernel.org/stable/c/28f7ff5e7559d226e63c7c5de74eb075a83d8c53 (opens in a new tab)
- https://git.kernel.org/stable/c/75205f1b47a88c3fac4f30bd7567e89b2887c7fd (opens in a new tab)
- https://git.kernel.org/stable/c/a636772988bafab89278e7bb3420d8e8eacfe912 (opens in a new tab)
- https://git.kernel.org/stable/c/dce0589a3faec9e2e543e97bca7e62592ec85585 (opens in a new tab)
- https://git.kernel.org/stable/c/bc68e428d4963af0201e92159629ab96948f0893 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2022-49780)Record last updated .