CVE-2022-50575
published 2025-10-22CVE-2022-50575: 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…
PriorityP420low3.3
EPSS
0.21%
10.7th percentile
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.
Affected
19 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.4-1 (bookworm) | linux 6.1.4-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 3ad0876554cafa368f574d4d408468510543e9ff < 5d68ae32d132ea2af73bc223fd64c46f85302a8b | 5d68ae32d132ea2af73bc223fd64c46f85302a8b |
| linux | linux | >= 3ad0876554cafa368f574d4d408468510543e9ff < 4f983ee5e5de924d93a7bbb4e6f68f38c6256cd5 | 4f983ee5e5de924d93a7bbb4e6f68f38c6256cd5 |
| linux | linux | >= 3ad0876554cafa368f574d4d408468510543e9ff < 46026bb057c35f5bb111bf95e00cd8366d2e34d4 | 46026bb057c35f5bb111bf95e00cd8366d2e34d4 |
| linux | linux | >= 3ad0876554cafa368f574d4d408468510543e9ff < 0bf874183b32eae2cc20e3c5be38ec3d33e7e564 | 0bf874183b32eae2cc20e3c5be38ec3d33e7e564 |
| linux | linux | >= 3ad0876554cafa368f574d4d408468510543e9ff < e0c5f1058ed96f2b7487560c4c4cbd768d13d065 | e0c5f1058ed96f2b7487560c4c4cbd768d13d065 |
| linux | linux | >= 3ad0876554cafa368f574d4d408468510543e9ff < 4da411086f5ab32f811a89ef804980ec106ebb65 | 4da411086f5ab32f811a89ef804980ec106ebb65 |
| linux | linux | >= 3ad0876554cafa368f574d4d408468510543e9ff < 8b997b2bb2c53b76a6db6c195930e9ab8e4b0c79 | 8b997b2bb2c53b76a6db6c195930e9ab8e4b0c79 |
| linux | linux_kernel | >= 0 < 5.10.178-1 | 5.10.178-1 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 4.18.0 < 4.19.270 | 4.19.270 |
| linux | linux_kernel | >= 4.20.0 < 5.4.229 | 5.4.229 |
| linux | linux_kernel | >= 5.11.0 < 5.15.86 | 5.15.86 |
| linux | linux_kernel | >= 5.16.0 < 6.0.16 | 6.0.16 |
| linux | linux_kernel | >= 5.5.0 < 5.10.163 | 5.10.163 |
| linux | linux_kernel | >= 6.1.0 < 6.1.2 | 6.1.2 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource()
vendor_redhat·2025-10-22·CVSS 3.3
CVE-2022-50575 [LOW] kernel: xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource()
kernel: xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource()
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.
Package: kernel (Red Hat Enterprise Linux 10) - Not affected
Package: kernel (Red Hat Enterprise Linux 6) - Not affected
Package: kernel (Red Hat Enterprise Linux 7) - Fix deferred
Package: kernel-rt (Red Hat Enterpris
Debian
CVE-2022-50575: linux - In the Linux kernel, the following vulnerability has been resolved: xen/privcmd...
vendor_debian·2022
CVE-2022-50575 CVE-2022-50575: linux - In the Linux kernel, the following vulnerability has been resolved: xen/privcmd...
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.
Scope: local
bookworm: resolved (fixed in 6.1.4-1)
bullseye: resolved (fixed in 5.10.178-1)
forky: resolved (fixed in 6.1.4-1)
sid: resolved (fixed in 6.1.4-1)
trixie: resolved (fixed in 6.1.4-1)
OSV
xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource()
osv·2025-10-22
CVE-2022-50575 xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource()
xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource()
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.
OSV
CVE-2022-50575: In the Linux kernel, the following vulnerability has been resolved: xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource() As 'kdata
osv·2025-10-22
CVE-2022-50575 CVE-2022-50575: In the Linux kernel, the following vulnerability has been resolved: xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource() As 'kdata
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.
GHSA
GHSA-jhf6-8mmm-jxfr: In the Linux kernel, the following vulnerability has been resolved:
xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource()
As 'kdata
ghsa_unreviewed·2025-10-22
CVE-2022-50575 GHSA-jhf6-8mmm-jxfr: In the Linux kernel, the following vulnerability has been resolved:
xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource()
As 'kdata
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.
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/0bf874183b32eae2cc20e3c5be38ec3d33e7e564https://git.kernel.org/stable/c/46026bb057c35f5bb111bf95e00cd8366d2e34d4https://git.kernel.org/stable/c/4da411086f5ab32f811a89ef804980ec106ebb65https://git.kernel.org/stable/c/4f983ee5e5de924d93a7bbb4e6f68f38c6256cd5https://git.kernel.org/stable/c/5d68ae32d132ea2af73bc223fd64c46f85302a8bhttps://git.kernel.org/stable/c/8b997b2bb2c53b76a6db6c195930e9ab8e4b0c79https://git.kernel.org/stable/c/e0c5f1058ed96f2b7487560c4c4cbd768d13d065
2025-10-22
Published