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-50226crypto: ccp - Use kzalloc for sev ioctl interfaces to prevent kernel memory leak

Description

In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Use kzalloc for sev ioctl interfaces to prevent kernel memory leak For some sev ioctl interfaces, input may be passed that is less than or equal to SEV_FW_BLOB_MAX_SIZE, but larger than the data that PSP firmware returns. In this case, kmalloc will allocate memory that is the size of the input rather than the size of the data. Since PSP firmware doesn't fully overwrite the buffer, the sev ioctl interfaces with the issue may return uninitialized slab memory. Currently, all of the ioctl interfaces in the ccp driver are safe, but to prevent future problems, change all ioctl interfaces that allocate memory with kmalloc to use kzalloc and memset the data buffer to zero in sev_ioctl_do_platform_status.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 11 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

CVSS scores of CVE-2022-50226, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (12 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected e799035609e1526761aa2f896a974b233d04d36d – < 4c5300f6f5e18b11c02a92f136e69b98fddba15e
    • affected e799035609e1526761aa2f896a974b233d04d36d – < f2a920daa780956b987c14b9f23de7c3c8915bf2
    • affected e799035609e1526761aa2f896a974b233d04d36d – < caa395aa16e7c9193fd7fa6cde462dd8229d4953
    • affected e799035609e1526761aa2f896a974b233d04d36d – < e11fb0a3a39bb42da35fa662c46ce7391f277436
    • affected e799035609e1526761aa2f896a974b233d04d36d – < 13dc15a3f5fd7f884e4bfa8c011a0ae868df12ae
  • Linux · Linux

    • affected 4.16
    • unaffected < 4.16
    • unaffected 5.10.173 – ≤ 5.10.*
    • unaffected 5.15.61 – ≤ 5.15.*
    • unaffected 5.18.18 – ≤ 5.18.*
    • unaffected 5.19.2 – ≤ 5.19.*
    • unaffected 6.0 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .