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.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 versions
Linux kernel versions
4.18
and later are affected. Fixed in
4.19.270,
5.4.229,
5.10.163,
5.15.86,
6.0.16,
6.1.2,
6.2
and their respective stable series.
References
The following references provide additional information about CVE-2022-50575 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.
-
PatchKernel patch commithttps://git.kernel.org/stable/c/0bf874183b32eae2cc20e3c5be38ec3d33e7e564
-
PatchKernel patch commithttps://git.kernel.org/stable/c/46026bb057c35f5bb111bf95e00cd8366d2e34d4
-
PatchKernel patch commithttps://git.kernel.org/stable/c/4da411086f5ab32f811a89ef804980ec106ebb65
Frequently asked questions
-
What is CVE-2022-50575?
CVE-2022-50575 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 4.18 onward and has been patched in 4.19.270, 5.4.229, 5.10.163 and others. CVE-2022-50575 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2022-50575?
Yes — CVE-2022-50575 has been patched. Fixed versions include 4.19.270, 5.4.229, 5.10.163 and others. If you are running Linux kernel 4.18 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2022-50575 actively exploited?
No — CVE-2022-50575 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.