Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2022-50575xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource()

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 7 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 3ad0876554cafa368f574d4d408468510543e9ff – < 5d68ae32d132ea2af73bc223fd64c46f85302a8b
    • affected 3ad0876554cafa368f574d4d408468510543e9ff – < 4f983ee5e5de924d93a7bbb4e6f68f38c6256cd5
    • affected 3ad0876554cafa368f574d4d408468510543e9ff – < 46026bb057c35f5bb111bf95e00cd8366d2e34d4
    • affected 3ad0876554cafa368f574d4d408468510543e9ff – < 0bf874183b32eae2cc20e3c5be38ec3d33e7e564
    • affected 3ad0876554cafa368f574d4d408468510543e9ff – < e0c5f1058ed96f2b7487560c4c4cbd768d13d065
    • affected 3ad0876554cafa368f574d4d408468510543e9ff – < 4da411086f5ab32f811a89ef804980ec106ebb65
    • affected 3ad0876554cafa368f574d4d408468510543e9ff – < 8b997b2bb2c53b76a6db6c195930e9ab8e4b0c79
  • Linux · Linux

    • affected 4.18
    • unaffected < 4.18
    • unaffected 4.19.270 – ≤ 4.19.*
    • unaffected 5.4.229 – ≤ 5.4.*
    • unaffected 5.10.163 – ≤ 5.10.*
    • unaffected 5.15.86 – ≤ 5.15.*
    • unaffected 6.0.16 – ≤ 6.0.*
    • unaffected 6.1.2 – ≤ 6.1.*
    • unaffected 6.2 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-50575 badge
[![CVE-2022-50575](https://cveledger.app/badge/CVE-2022-50575.svg)](https://cveledger.app/cve/CVE-2022-50575)

Record last updated .