xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3ad0876554cafa368f574d4d408468510543e9ff · < 4da411086f5ab32f811a89ef804980ec106ebb65| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's xen/privcmd ioctl can produce a stack trace and warning in dmesg when a user requests an allocation that is too large. A local user can trigger this by passing a large value to privcmd_ioctl_mmap_resource(); no further user interaction is described.
Operators running the Linux kernel should check whether their version includes the xen/privcmd fix; affected versions are not specified.