Linux Kernel up to 6.1.1 xen privcmd_ioctl_mmap_resource allocation of resources

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Linux Kernel up to 6.1.1. Affected by this issue is the function privcmd_ioctl_mmap_resource of the component xen. Performing a manipulation results in allocation of resources.
This vulnerability is cataloged as CVE-2022-50575. There is no exploit available.
It is suggested to upgrade the affected component.
Details
A vulnerability classified as critical has been found in Linux Kernel up to 6.1.1. This affects the function privcmd_ioctl_mmap_resource of the component xen. The manipulation with an unknown input leads to a allocation of resources vulnerability. CWE is classifying the issue as CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. The impact remains unknown. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource() As 'kdata.num' is user-controlled data, if user tries to allocate memory larger than(>=) MAX_ORDER, then kcalloc() will fail, it creates a stack trace and messes up dmesg with a warning. Call trace: -> privcmd_ioctl --> privcmd_ioctl_mmap_resource Add __GFP_NOWARN in order to avoid too large allocation warning. This is detected by static analysis using smatch.
It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2022-50575 since 10/22/2025. The exploitability is told to be difficult. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 4.19.270, 5.4.229, 5.10.163, 5.15.86, 6.0.16 or 6.1.2 eliminates this vulnerability. Applying the patch 5d68ae32d132ea2af73bc223fd64c46f85302a8b/4f983ee5e5de924d93a7bbb4e6f68f38c6256cd5/46026bb057c35f5bb111bf95e00cd8366d2e34d4/0bf874183b32eae2cc20e3c5be38ec3d33e7e564/e0c5f1058ed96f2b7487560c4c4cbd768d13d065/4da411086f5ab32f811a89ef804980ec106ebb65/8b997b2bb2c53b76a6db6c195930e9ab8e4b0c79 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 vulnerability database at CERT Bund (WID-SEC-2025-2394). Be aware that VulDB is the high quality source for vulnerability data.
Affected
- Red Hat Enterprise Linux
- SUSE Linux
- Oracle Linux
- Open Source Linux Kernel
- Dell NetWorker
Product
Type
Vendor
Name
Version
- 4.19.269
- 5.4.228
- 5.10.162
- 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.15.64
- 5.15.65
- 5.15.66
- 5.15.67
- 5.15.68
- 5.15.69
- 5.15.70
- 5.15.71
- 5.15.72
- 5.15.73
- 5.15.74
- 5.15.75
- 5.15.76
- 5.15.77
- 5.15.78
- 5.15.79
- 5.15.80
- 5.15.81
- 5.15.82
- 5.15.83
- 5.15.84
- 5.15.85
- 6.0.0
- 6.0.1
- 6.0.2
- 6.0.3
- 6.0.4
- 6.0.5
- 6.0.6
- 6.0.7
- 6.0.8
- 6.0.9
- 6.0.10
- 6.0.11
- 6.0.12
- 6.0.13
- 6.0.14
- 6.0.15
- 6.1.0
- 6.1.1
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.6VulDB Meta Temp Score: 4.4
VulDB Base Score: 4.6
VulDB Temp Score: 4.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Allocation of resourcesCWE: CWE-770 / CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 4.19.270/5.4.229/5.10.163/5.15.86/6.0.16/6.1.2
Patch: 5d68ae32d132ea2af73bc223fd64c46f85302a8b/4f983ee5e5de924d93a7bbb4e6f68f38c6256cd5/46026bb057c35f5bb111bf95e00cd8366d2e34d4/0bf874183b32eae2cc20e3c5be38ec3d33e7e564/e0c5f1058ed96f2b7487560c4c4cbd768d13d065/4da411086f5ab32f811a89ef804980ec106ebb65/8b997b2bb2c53b76a6db6c195930e9ab8e4b0c79
Timeline
10/22/2025 Advisory disclosed10/22/2025 CVE reserved
10/22/2025 VulDB entry created
02/28/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2022-50575 (🔒)
GCVE (CVE): GCVE-0-2022-50575
GCVE (VulDB): GCVE-100-329319
CERT Bund: WID-SEC-2025-2394 - Linux Kernel: Mehrere Schwachstellen
Entry
Created: 10/22/2025 16:28Updated: 02/28/2026 08:30
Changes: 10/22/2025 16:28 (59), 10/24/2025 05:32 (7), 01/02/2026 04:11 (1), 02/28/2026 08:30 (1)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.