Bug 2405736 (CVE-2022-50575) - CVE-2022-50575 kernel: xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource()
Summary: CVE-2022-50575 kernel: xen/privcmd: Fix a possible warning in privcmd_ioctl_m...
Keywords:
Status: NEW
Alias: CVE-2022-50575
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-10-22 14:03 UTC by OSIDB Bzimport
Modified: 2025-10-22 17:39 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-10-22 14:03:24 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.