CVE-2022-49620: net: tipc: fix possible refcount leak in tipc_sk_create()
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.26% (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 00aff3590fc0a73bddd3b743863c14e76fd35c0c, 3b2957fc09fe1ac7f07f40dd50dd5f93e3f3a7a2, 4919d82f7041157a421ca9bf39a78551d5ad8a1b.
Low priority for now. Upgrade to Linux Linux 00aff3590fc0a73bddd3b743863c14e76fd35c0c, 3b2957fc09fe1ac7f07f40dd50dd5f93e3f3a7a2, 4919d82f7041157a421ca9bf39a78551d5ad8a1b 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: net: tipc: fix possible refcount leak in tipc_sk_create() Free sk in case tipc_sk_insert() fails.
- Published
- Feb 26, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 18th percentile
- CWE
- —
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%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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 kernelbefore 4.9.324
- linux linux kernel4.10 and later · before 4.14.289
- linux linux kernel4.15 and later · before 4.19.253
- linux linux kernel4.20 and later · before 5.4.207
- linux linux kernel5.5 and later · before 5.10.132
- linux linux kernel5.11 and later · before 5.15.56
- linux linux kernel5.16 and later · before 5.18.13
- linux linux kernel5.19
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
- 3.18affected
- 5b8fa7ce823a59a328e0a7661df2478bfb745de4 and later · before 638fa20b618b2bbcf86da71231624cc82121a036affected · git
- 5b8fa7ce823a59a328e0a7661df2478bfb745de4 and later · before 7bc9e7f70bc57d8f02ffea2a42094281effb15efaffected · git
- 5b8fa7ce823a59a328e0a7661df2478bfb745de4 and later · before ef488669b2652bde5b6ee5a409a5b048a2a50db4affected · git
- 5b8fa7ce823a59a328e0a7661df2478bfb745de4 and later · before 4919d82f7041157a421ca9bf39a78551d5ad8a1baffected · git
- 5b8fa7ce823a59a328e0a7661df2478bfb745de4 and later · before efa78f2ae363428525fb4981bb63c555ee79f3c7affected · git
- 5b8fa7ce823a59a328e0a7661df2478bfb745de4 and later · before 833ecd0eae76eadf81d6d747bb5bc992d1151867affected · git
- 5b8fa7ce823a59a328e0a7661df2478bfb745de4 and later · before 3b2957fc09fe1ac7f07f40dd50dd5f93e3f3a7a2affected · git
- 5b8fa7ce823a59a328e0a7661df2478bfb745de4 and later · before 00aff3590fc0a73bddd3b743863c14e76fd35c0caffected · git
- before 3.18not 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 5.18.14-1 | 5.18.14-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-49618Feb 26, 2025 · pinctrl: aspeed: Fix potential NULL dereference in aspeed_pinmux_set_mux()22Monitor
- ← EarlierCVE-2022-49619Feb 26, 2025 · net: sfp: fix memory leak in sfp_probe()22Monitor
- Later →CVE-2022-49621Feb 26, 2025 · cpufreq: pmac32-cpufreq: Fix refcount leak bug22Monitor
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 | 00aff3590fc0a73bddd3b743863c14e76fd35c0c | Vendor (CNA) |
| Linux Linux | 3b2957fc09fe1ac7f07f40dd50dd5f93e3f3a7a2 | Vendor (CNA) |
| Linux Linux | 4919d82f7041157a421ca9bf39a78551d5ad8a1b | Vendor (CNA) |
| Linux Linux | 638fa20b618b2bbcf86da71231624cc82121a036 | Vendor (CNA) |
| Linux Linux | 7bc9e7f70bc57d8f02ffea2a42094281effb15ef | Vendor (CNA) |
| Linux Linux | 833ecd0eae76eadf81d6d747bb5bc992d1151867 | Vendor (CNA) |
| Linux Linux | ef488669b2652bde5b6ee5a409a5b048a2a50db4 | Vendor (CNA) |
| Linux Linux | efa78f2ae363428525fb4981bb63c555ee79f3c7 | Vendor (CNA) |
| debian:linux | 5.18.14-1 · Debian:12 | 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.
No history yet (it accumulates with the daily EPSS job).
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)
—
CVSS 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 (7 more)Show less
- git.kernel.org/stable/c/3b2957fc09fe1ac7f07f40dd50dd5f93e3f3a7a2
- git.kernel.org/stable/c/4919d82f7041157a421ca9bf39a78551d5ad8a1b
- git.kernel.org/stable/c/638fa20b618b2bbcf86da71231624cc82121a036
- git.kernel.org/stable/c/7bc9e7f70bc57d8f02ffea2a42094281effb15ef
- git.kernel.org/stable/c/833ecd0eae76eadf81d6d747bb5bc992d1151867
- git.kernel.org/stable/c/ef488669b2652bde5b6ee5a409a5b048a2a50db4
- git.kernel.org/stable/c/efa78f2ae363428525fb4981bb63c555ee79f3c7
Vendor advisories and official records. Exploit/PoC links are deliberately left out.