CVE-2022-50575: xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Fixed version: Linux Linux 0bf874183b32eae2cc20e3c5be38ec3d33e7e564, 46026bb057c35f5bb111bf95e00cd8366d2e34d4, 4da411086f5ab32f811a89ef804980ec106ebb65.
Low priority for now. Upgrade to Linux Linux 0bf874183b32eae2cc20e3c5be38ec3d33e7e564, 46026bb057c35f5bb111bf95e00cd8366d2e34d4, 4da411086f5ab32f811a89ef804980ec106ebb65 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 22, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.18affected
- 3ad0876554cafa368f574d4d408468510543e9ff and later · before 5d68ae32d132ea2af73bc223fd64c46f85302a8baffected · git
- 3ad0876554cafa368f574d4d408468510543e9ff and later · before 4f983ee5e5de924d93a7bbb4e6f68f38c6256cd5affected · git
- 3ad0876554cafa368f574d4d408468510543e9ff and later · before 46026bb057c35f5bb111bf95e00cd8366d2e34d4affected · git
- 3ad0876554cafa368f574d4d408468510543e9ff and later · before 0bf874183b32eae2cc20e3c5be38ec3d33e7e564affected · git
- 3ad0876554cafa368f574d4d408468510543e9ff and later · before e0c5f1058ed96f2b7487560c4c4cbd768d13d065affected · git
- 3ad0876554cafa368f574d4d408468510543e9ff and later · before 4da411086f5ab32f811a89ef804980ec106ebb65affected · git
- 3ad0876554cafa368f574d4d408468510543e9ff and later · before 8b997b2bb2c53b76a6db6c195930e9ab8e4b0c79affected · git
- before 4.18not affected · semver
- 4.19.270 and later · up to and including 4.19.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.4-1 | 6.1.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2022-50573Oct 22, 2025 · wifi: mt76: mt7915: fix mt7915_rate_txpower_get() resource leaks0Monitor
- ← EarlierCVE-2022-50574Oct 22, 2025 · drm/omap: dss: Fix refcount leak bugs0Monitor
- Later →CVE-2022-50576Oct 22, 2025 · serial: pch: Fix PCI device refcount leak in pch_request_dma()0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0bf874183b32eae2cc20e3c5be38ec3d33e7e564 | Vendor (CNA) |
| Linux Linux | 46026bb057c35f5bb111bf95e00cd8366d2e34d4 | Vendor (CNA) |
| Linux Linux | 4da411086f5ab32f811a89ef804980ec106ebb65 | Vendor (CNA) |
| Linux Linux | 4f983ee5e5de924d93a7bbb4e6f68f38c6256cd5 | Vendor (CNA) |
| Linux Linux | 5d68ae32d132ea2af73bc223fd64c46f85302a8b | Vendor (CNA) |
| Linux Linux | 8b997b2bb2c53b76a6db6c195930e9ab8e4b0c79 | Vendor (CNA) |
| Linux Linux | e0c5f1058ed96f2b7487560c4c4cbd768d13d065 | Vendor (CNA) |
| debian:linux | 6.1.4-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/46026bb057c35f5bb111bf95e00cd8366d2e34d4
- git.kernel.org/stable/c/4da411086f5ab32f811a89ef804980ec106ebb65
- git.kernel.org/stable/c/4f983ee5e5de924d93a7bbb4e6f68f38c6256cd5
- git.kernel.org/stable/c/5d68ae32d132ea2af73bc223fd64c46f85302a8b
- git.kernel.org/stable/c/8b997b2bb2c53b76a6db6c195930e9ab8e4b0c79
- git.kernel.org/stable/c/e0c5f1058ed96f2b7487560c4c4cbd768d13d065
Vendor advisories and official records. Exploit/PoC links are deliberately left out.