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

Medium 5.5 Published Updated

A memory leak in the Linux kernel's tcm_loop driver can lead to resource exhaustion and denial of service if device registration fails.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2022-49780?

CVE-2022-49780 is a medium-severity memory corruption vulnerability in Linux kernel, published on 1 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

Official 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.

Weakness: CWE-401

Which versions are affected by CVE-2022-49780?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2022-49780?

Apply the vendor's patch.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2022-49780 being exploited?

There is no known exploitation of CVE-2022-49780 in the wild and no public exploit code.

All Linux kernel vulnerabilities

Sources

Also known as DEBIAN-CVE-2022-49780, GHSA-px2q-r9rv-q5m3, UBUNTU-CVE-2022-49780.

Is CVE-2022-49780 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free