LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50707: virtio-crypto: fix memory leak in virtio_crypto_alg_skcipher_close_session()

In the Linux kernel, the following vulnerability has been resolved: virtio-crypto: fix memory leak in virtio_crypto_alg_skcipher_close_session() 'vc_ctrl_req' is alloced in virtio_crypto_alg_skcipher_close_session(), and should be freed in the invalid ctrl_status->status error handling case. Otherwise there is a memory leak.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-50707 is a Linux kernel virtio-crypto memory leak. In a specific error-handling path while closing a crypto session, memory may not be freed. The public bundle does not provide CVSS, confirmed exploitation, or business-impact details.

Executive priority

Schedule remediation through normal kernel maintenance unless vendor guidance raises severity. Prioritize virtualized Linux assets using virtio-crypto and systems with tight availability requirements.

Technical view

The flaw is in virtio_crypto_alg_skcipher_close_session(). The allocated vc_ctrl_req object is not freed when ctrl_status->status indicates an invalid status, causing a memory leak. The issue is marked resolved in Linux stable commits, but the supplied data does not define exploit prerequisites or impact severity.

Likely exposure

Exposure appears limited to Linux systems running affected kernels with virtio-crypto present or enabled. The bundle lists Linux as affected around versions 5.19, 6.0.19, 6.1.5, and 6.2, but exact range semantics are incomplete.

Exploitation context

The source bundle does not cite active exploitation, public exploit availability, or KEV listing. Treat this as an operational reliability and potential denial-of-service concern until vendor advisories clarify reachability and impact.

Researcher notes

The record is sparse: no CVSS, CWE, exploitability assessment, or precise affected-version ranges are provided. Analysis should focus on commit review, distribution backports, and whether the error path is reachable in local deployment conditions.

Mitigation direction

  • Check Linux distribution advisories for CVE-2022-50707 and virtio-crypto backports.
  • Update affected kernels to vendor builds containing the referenced stable fixes.
  • Prioritize systems using virtualization stacks where virtio-crypto is available.
  • Track kernel package versions against distribution security notices, not only upstream version numbers.

Validation and detection

  • Inventory Linux kernel versions and package release metadata across virtualized hosts and guests.
  • Confirm whether virtio-crypto modules or devices are present on relevant systems.
  • Map installed kernels to vendor advisories or the referenced stable commits.
  • Review monitoring for unusual kernel memory growth on systems using virtio-crypto.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50707 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4ee475e76b5ea8061970a7c867ffa5eedeb39580, 0756ad15b1fef287d4d8fa11bc36ea77a5c42e4a, 0756ad15b1fef287d4d8fa11bc36ea77a5c42e4a, 0756ad15b1fef287d4d8fa11bc36ea77a5c42e4aunaffected
LinuxLinux5.19, 0, 6.0.19, 6.1.5, 6.2affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.