CVE-2022-50575

xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource()

N/A

Published: October 22, 2025 at 01:23 PM UTC

Updated: June 17, 2026 at 05:23 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

N/A

Exploit prediction

EPSS 0.2%

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

4.18 ≤ v < 4.19.2704.18 ≤ v < 5.10.1634.18 ≤ v < 5.15.864.18 ≤ v < 5.4.2294.18 ≤ v < 6.0.164.18 ≤ v < 6.1.24.18 ≤ v < 6.23ad0876554cafa368f574d4d408468510543e9ff4.18

Vendor states this is fixed in 0bf874183b32eae2cc20e3c5be38ec3d33e7e564 (fixed)

Vendor states this is fixed in 46026bb057c35f5bb111bf95e00cd8366d2e34d4 (fixed)

Vendor states this is fixed in 4da411086f5ab32f811a89ef804980ec106ebb65 (fixed)

Vendor states this is fixed in 4f983ee5e5de924d93a7bbb4e6f68f38c6256cd5 (fixed)

Vendor states this is fixed in 5d68ae32d132ea2af73bc223fd64c46f85302a8b (fixed)

Vendor states this is fixed in 8b997b2bb2c53b76a6db6c195930e9ab8e4b0c79 (fixed)

Vendor states this is fixed in e0c5f1058ed96f2b7487560c4c4cbd768d13d065 (fixed)

Vendor states this is fixed in 4.18 (unaffected)

Vendor states this is fixed in 4.19.270 (unaffected)

Vendor states this is fixed in 5.10.163 (unaffected)

Vendor states this is fixed in 5.15.86 (unaffected)

Vendor states this is fixed in 5.4.229 (unaffected)