CVE-2022-49780: scsi: target: tcm_loop: Fix possible name leak in tcm_loop_setup_hba_bus()
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 28f7ff5e7559d226e63c7c5de74eb075a83d8c53, 41a6b8b527a5957fab41c3c05e25ad125268e2e9, 75205f1b47a88c3fac4f30bd7567e89b2887c7fd.
Low priority for now. Upgrade to Linux Linux 28f7ff5e7559d226e63c7c5de74eb075a83d8c53, 41a6b8b527a5957fab41c3c05e25ad125268e2e9, 75205f1b47a88c3fac4f30bd7567e89b2887c7fd or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 1, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-401
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.39 and later · before 4.19.267
- linux linux kernel4.20 and later · before 5.4.225
- linux linux kernel5.5 and later · before 5.10.156
- linux linux kernel5.11 and later · before 5.15.80
- linux linux kernel5.16 and later · before 6.0.10
- linux linux kernel6.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.39affected
- 3703b2c5d041a68095cdd22380c23ce27d449ad7 and later · before 41a6b8b527a5957fab41c3c05e25ad125268e2e9affected · git
- 3703b2c5d041a68095cdd22380c23ce27d449ad7 and later · before 28f7ff5e7559d226e63c7c5de74eb075a83d8c53affected · git
- 3703b2c5d041a68095cdd22380c23ce27d449ad7 and later · before 75205f1b47a88c3fac4f30bd7567e89b2887c7fdaffected · git
- 3703b2c5d041a68095cdd22380c23ce27d449ad7 and later · before a636772988bafab89278e7bb3420d8e8eacfe912affected · git
- 3703b2c5d041a68095cdd22380c23ce27d449ad7 and later · before dce0589a3faec9e2e543e97bca7e62592ec85585affected · git
- 3703b2c5d041a68095cdd22380c23ce27d449ad7 and later · before bc68e428d4963af0201e92159629ab96948f0893affected · git
- before 2.6.39not affected · semver
- 4.19.267 and later · up to and including 4.19.*not affected · semver
- 5.4.225 and later · up to and including 5.4.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.0.10-1 | 6.0.10-1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kernel-default | before 4.12.14-122.266.1 | 4.12.14-122.266.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_70 | before 1-8.5.1 | 1-8.5.1 |
| SUSE:Linux Enterprise Server 12 SP5-LTSS | kernel-source | before 4.12.14-122.266.1 | 4.12.14-122.266.1 |
| SUSE:Linux Enterprise Server 12 SP5-LTSS | kernel-syms | before 4.12.14-122.266.1 | 4.12.14-122.266.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-49778May 1, 2025 · arm64/mm: fix incorrect file_map_count for non-leaf pmd/pud22Monitor
- ← EarlierCVE-2022-49779May 1, 2025 · kprobes: Skip clearing aggrprobe's post_handler in kprobe-on-ftrace case31Monitor
- Later →CVE-2022-49781May 1, 2025 · perf/x86/amd: Fix crash due to race between amd_pmu_enable_all, perf NMI and throttling18Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 28f7ff5e7559d226e63c7c5de74eb075a83d8c53 | Vendor (CNA) |
| Linux Linux | 41a6b8b527a5957fab41c3c05e25ad125268e2e9 | Vendor (CNA) |
| Linux Linux | 75205f1b47a88c3fac4f30bd7567e89b2887c7fd | Vendor (CNA) |
| Linux Linux | a636772988bafab89278e7bb3420d8e8eacfe912 | Vendor (CNA) |
| Linux Linux | bc68e428d4963af0201e92159629ab96948f0893 | Vendor (CNA) |
| Linux Linux | dce0589a3faec9e2e543e97bca7e62592ec85585 | Vendor (CNA) |
| debian:linux | 6.0.10-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-default | 4.12.14-122.266.1 · SUSE:Linux Enterprise Live Patching 12 SP5 | Package registry (OSV) |
| suse:kernel-source | 4.12.14-122.266.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS | Package registry (OSV) |
| suse:kernel-syms | 4.12.14-122.266.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS | Package registry (OSV) |
| suse:kgraft-patch-SLE12-SP5_Update_70 | 1-8.5.1 · SUSE:Linux Enterprise Live Patching 12 SP5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-401 · Missing Release of Memory after Effective LifetimeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/41a6b8b527a5957fab41c3c05e25ad125268e2e9
- git.kernel.org/stable/c/75205f1b47a88c3fac4f30bd7567e89b2887c7fd
- git.kernel.org/stable/c/a636772988bafab89278e7bb3420d8e8eacfe912
- git.kernel.org/stable/c/bc68e428d4963af0201e92159629ab96948f0893
- git.kernel.org/stable/c/dce0589a3faec9e2e543e97bca7e62592ec85585
Vendor advisories and official records. Exploit/PoC links are deliberately left out.