CVE-2022-49780 [Medium] | Information Disclosure in Linux Kernel

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-02-25	0.03%	0.05%	+0.03%
2	2025-11-08	0.10%	0.03%	-0.07%
3	2025-07-16	—	0.10%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-02-25

0.03%

0.05%

+0.03%

2025-11-08

0.10%

0.03%

-0.07%

2025-07-16

—

0.10%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

3.6

[email protected]

OS Trackers for CVE-2022-49780

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-49780 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2022-49780
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2022-49780
`suse`	medium	CVE-2022-49780 severity moderate: SUSE including 271 source package names (amazon/suse-sles-15-sp1-chost-byos-v20210304-hvm-ssd-x86_64, amazon/suse-sles-15-sp1-chost-byos-v20220127-hvm-ssd-x86_64, …), 384 product×package rows across 35 product lines (Image SLES12-SP5-Azure-BYOS, Image SLES12-SP5-Azure-HPC-BYOS, … (35 product lines)): Known Affected 231, Fixed 77, Known Not Affected 76.	https://www.suse.com/security/cve/CVE-2022-49780/
`ubuntu`	medium	CVE-2022-49780 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1551 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1145, released 154, ignored 149, not-affected 98, needed 4, needs-triage 1.	https://ubuntu.com/security/CVE-2022-49780

Affected software / configurations for CVE-2022-49780

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 2.6.39, < 4.19.267	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.20, < 5.4.225	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.5, < 5.10.156	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.80	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 6.0.10	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	6.1	cpe:2.3:o:linux:linux_kernel:6.1:rc1::::::
linux	linux_kernel	6.1	cpe:2.3:o:linux:linux_kernel:6.1:rc2::::::
linux	linux_kernel	6.1	cpe:2.3:o:linux:linux_kernel:6.1:rc3::::::
linux	linux_kernel	6.1	cpe:2.3:o:linux:linux_kernel:6.1:rc4::::::
linux	linux_kernel	6.1	cpe:2.3:o:linux:linux_kernel:6.1:rc5::::::

References for CVE-2022-49780

URL	Tags
https://git.kernel.org/stable/c/28f7ff5e7559d226e63c7c5de74eb075a83d8c53	Patch
https://git.kernel.org/stable/c/41a6b8b527a5957fab41c3c05e25ad125268e2e9	Patch
https://git.kernel.org/stable/c/75205f1b47a88c3fac4f30bd7567e89b2887c7fd	Patch
https://git.kernel.org/stable/c/a636772988bafab89278e7bb3420d8e8eacfe912	Patch
https://git.kernel.org/stable/c/bc68e428d4963af0201e92159629ab96948f0893	Patch
https://git.kernel.org/stable/c/dce0589a3faec9e2e543e97bca7e62592ec85585	Patch

URL

CVE-2022-49780 | scsi: target: tcm_loop: Fix possible name leak in tcm_loop_setup_hba_bus()

Exploit prediction scoring system (EPSS) score for CVE-2022-49780

Common vulnerability scoring system (CVSS) metrics for CVE-2022-49780

Weakness enumeration for CVE-2022-49780

OS Trackers for CVE-2022-49780

Affected software / configurations for CVE-2022-49780

References for CVE-2022-49780