Linux Kernel up to 5.19.5 xfrm __xfrm_policy_check reference count

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Linux Kernel up to 5.19.5. It has been classified as critical. Affected by this issue is the function __xfrm_policy_check of the component xfrm. Performing a manipulation results in reference count.
This vulnerability is reported as CVE-2022-50007. No exploit exists.
Upgrading the affected component is recommended.
Details
A vulnerability was found in Linux Kernel up to 5.19.5. It has been classified as critical. This affects the function __xfrm_policy_check of the component xfrm. The manipulation with an unknown input leads to a reference count vulnerability. CWE is classifying the issue as CWE-911. The product uses a reference count to manage a resource, but it does not update or incorrectly updates the reference count. This is going to have an impact on availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: xfrm: fix refcount leak in __xfrm_policy_check() The issue happens on an error path in __xfrm_policy_check(). When the fetching process of the object `pols[1]` fails, the function simply returns 0, forgetting to decrement the reference count of `pols[0]`, which is incremented earlier by either xfrm_sk_policy_lookup() or xfrm_policy_lookup(). This may result in memory leaks. Fix it by decreasing the reference count of `pols[0]` in that path.
The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2022-50007 since 06/18/2025. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 247361 (Linux Distros Unpatched Vulnerability : CVE-2022-50007), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 4.9.327, 4.14.292, 4.19.257, 5.4.212, 5.10.140, 5.15.64 or 5.19.6 eliminates this vulnerability. Applying the patch 18e6b6e2555c93f5ca09f2b85ef1fa025c8accea/8f94b933103ee1bda119543369cc18a1be5536db/0769491a8acd3e85ca4c3f65080eac2c824262df/63da7a2bbf3f28094920e0b8a17d2571a9bd842d/1305d7d4f35ca6f214a2d23b075aa6a924cff3be/26ad2398fe4984f4f6f930bcb3bc9047fa77265b/d66c052879791313f90c0584420f196a038fb8b8/9c9cb23e00ddf45679b21b4dacc11d1ae7961ebe is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (247361) and CERT Bund (WID-SEC-2025-1350). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- Debian Linux
- Amazon Linux 2
- Red Hat Enterprise Linux
- Ubuntu Linux
- SUSE Linux
- Oracle Linux
- SUSE openSUSE
- Open Source Linux Kernel
- RESF Rocky Linux
- Dell Avamar
- Dell NetWorker
- Dell Secure Connect Gateway
- IBM QRadar SIEM
Product
Type
Vendor
Name
Version
- 4.9.326
- 4.14.291
- 4.19.256
- 5.4.211
- 5.10.139
- 5.15.0
- 5.15.1
- 5.15.2
- 5.15.3
- 5.15.4
- 5.15.5
- 5.15.6
- 5.15.7
- 5.15.8
- 5.15.9
- 5.15.10
- 5.15.11
- 5.15.12
- 5.15.13
- 5.15.14
- 5.15.15
- 5.15.16
- 5.15.17
- 5.15.18
- 5.15.19
- 5.15.20
- 5.15.21
- 5.15.22
- 5.15.23
- 5.15.24
- 5.15.25
- 5.15.26
- 5.15.27
- 5.15.28
- 5.15.29
- 5.15.30
- 5.15.31
- 5.15.32
- 5.15.33
- 5.15.34
- 5.15.35
- 5.15.36
- 5.15.37
- 5.15.38
- 5.15.39
- 5.15.40
- 5.15.41
- 5.15.42
- 5.15.43
- 5.15.44
- 5.15.45
- 5.15.46
- 5.15.47
- 5.15.48
- 5.15.49
- 5.15.50
- 5.15.51
- 5.15.52
- 5.15.53
- 5.15.54
- 5.15.55
- 5.15.56
- 5.15.57
- 5.15.58
- 5.15.59
- 5.15.60
- 5.15.61
- 5.15.62
- 5.15.63
- 5.19.0
- 5.19.1
- 5.19.2
- 5.19.3
- 5.19.4
- 5.19.5
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Reference countCWE: CWE-911 / CWE-664
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 247361
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2022-50007
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 4.9.327/4.14.292/4.19.257/5.4.212/5.10.140/5.15.64/5.19.6
Patch: 18e6b6e2555c93f5ca09f2b85ef1fa025c8accea/8f94b933103ee1bda119543369cc18a1be5536db/0769491a8acd3e85ca4c3f65080eac2c824262df/63da7a2bbf3f28094920e0b8a17d2571a9bd842d/1305d7d4f35ca6f214a2d23b075aa6a924cff3be/26ad2398fe4984f4f6f930bcb3bc9047fa77265b/d66c052879791313f90c0584420f196a038fb8b8/9c9cb23e00ddf45679b21b4dacc11d1ae7961ebe
Timeline
06/18/2025 Advisory disclosed06/18/2025 CVE reserved
06/18/2025 VulDB entry created
11/30/2025 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2022-50007 (🔒)
GCVE (CVE): GCVE-0-2022-50007
GCVE (VulDB): GCVE-100-313017
CERT Bund: WID-SEC-2025-1350 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service
Entry
Created: 06/18/2025 14:58Updated: 11/30/2025 18:56
Changes: 06/18/2025 14:58 (59), 07/18/2025 01:25 (7), 07/29/2025 07:02 (1), 08/11/2025 01:25 (2), 10/19/2025 02:33 (1), 11/15/2025 07:02 (11), 11/30/2025 18:56 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.