CVE-2022-50575
Awaiting Analysis Awaiting Analysis - Queue
BaseFortify

Publication date: 2025-10-22

Last updated on: 2025-10-22

Assigner: kernel.org

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-10-22
Last Modified
2025-10-22
Generated
2026-05-07
AI Q&A
2025-10-22
EPSS Evaluated
2026-05-05
NVD
CVE-2022-50575
EUVD
EUVD-2022-55653
Affected Vendors & Products
Currently, no data is known.
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is in the Linux kernel's xen/privcmd component. It involves a possible warning triggered in the function privcmd_ioctl_mmap_resource() when user-controlled data 'kdata.num' attempts to allocate memory larger than or equal to MAX_ORDER. This causes the kcalloc() function to fail, resulting in a stack trace and cluttering the system log (dmesg) with warnings. The fix adds the __GFP_NOWARN flag to avoid these large allocation warnings.


How can this vulnerability impact me? :

The impact of this vulnerability is primarily that it can cause excessive warning messages and stack traces in the system logs (dmesg), which may clutter logs and potentially make it harder to diagnose other issues. There is no indication of a security breach or system compromise from this issue.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart