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

Status: published. Published: 2025-05-01. Updated: 2026-11-05.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ 3703b2c5d041a68095cdd22380c23ce27d449ad7; < 41a6b8b527a5957fab41c3c05e25ad125268e2e9 (affected, git); ≥ 3703b2c5d041a68095cdd22380c23ce27d449ad7; < 28f7ff5e7559d226e63c7c5de74eb075a83d8c53 (affected, git); ≥ 3703b2c5d041a68095cdd22380c23ce27d449ad7; < 75205f1b47a88c3fac4f30bd7567e89b2887c7fd (affected, git); ≥ 3703b2c5d041a68095cdd22380c23ce27d449ad7; < a636772988bafab89278e7bb3420d8e8eacfe912 (affected, git); ≥ 3703b2c5d041a68095cdd22380c23ce27d449ad7; < dce0589a3faec9e2e543e97bca7e62592ec85585 (affected, git); ≥ 3703b2c5d041a68095cdd22380c23ce27d449ad7; < bc68e428d4963af0201e92159629ab96948f0893 (affected, git). Source: CNA: Linux
- Linux / Linux: 2.6.39 (affected); ≥ 0; < 2.6.39 (unaffected, semver); ≥ 4.19.267; ≤ 4.19.* (unaffected, semver); ≥ 5.4.225; ≤ 5.4.* (unaffected, semver); ≥ 5.10.156; ≤ 5.10.* (unaffected, semver); ≥ 5.15.80; ≤ 5.15.* (unaffected, semver); ≥ 6.0.10; ≤ 6.0.* (unaffected, semver); ≥ 6.1; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: 0.22% as of 2026-11-05; percentile 12.10%

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/41a6b8b527a5957fab41c3c05e25ad125268e2e9 (CNA: Linux)

- https://git.kernel.org/stable/c/28f7ff5e7559d226e63c7c5de74eb075a83d8c53 (CNA: Linux)

- https://git.kernel.org/stable/c/75205f1b47a88c3fac4f30bd7567e89b2887c7fd (CNA: Linux)

- https://git.kernel.org/stable/c/a636772988bafab89278e7bb3420d8e8eacfe912 (CNA: Linux)

- https://git.kernel.org/stable/c/dce0589a3faec9e2e543e97bca7e62592ec85585 (CNA: Linux)

- https://git.kernel.org/stable/c/bc68e428d4963af0201e92159629ab96948f0893 (CNA: Linux)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2022-49780; retrieved 2026-11-05; source updated 2026-11-05

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2022-49780; retrieved 2026-11-05; source updated Not reported

Revision: 56e6154ca7141c42f6a23121652cd804aee8f8869bdc1a211c969a7f5359143f

Canonical: https://y2.dev/cve/CVE-2022-49780

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.