Security readout for executives and security teams
Plain-English summary
This is a Linux kernel SUNRPC memory leak fixed upstream. If the vulnerable error path is reached, kernel memory may not be freed. The public record does not provide severity, CVSS, exploitability, or impact beyond the leak description.
Executive priority
Handle as a kernel maintenance item with uncertain urgency. Patch through normal Linux update channels, escalating only if your vendor assigns severity or confirms exposure in critical systems.
Technical view
CVE-2022-50821 concerns gss_read_proxy_verf() in Linux SUNRPC. The resolved issue is that netobj memory was leaked when that function failed. The CVE lists Linux kernel versions and multiple stable commit references, but provides no CWE, CVSS vector, exploit preconditions, or demonstrated security outcome.
Likely exposure
Exposure is limited to Linux kernels containing the affected SUNRPC code. Relevance is higher where SUNRPC/GSS functionality is present, but the source bundle does not define reachable configurations or affected distributions.
Exploitation context
The source bundle does not report active exploitation, public exploit availability, or inclusion in CISA KEV. Treat exploitation status as unconfirmed, not known active.
Researcher notes
Evidence is sparse: the CVE text names a memory leak in a failure path and links stable commits. There is no public CVSS, CWE, exploit narrative, or affected configuration detail in the supplied bundle.
Mitigation direction
Check vendor kernel advisories for CVE-2022-50821 coverage.
Apply distribution kernel updates that include the referenced upstream fixes.
Track upstream stable commits if vendor guidance is not yet available.
Prioritize review of systems where SUNRPC/GSS functionality is enabled.
Validation and detection
Inventory running Linux kernel versions across managed systems.
Compare kernel packages against vendor backport notes for this CVE.
Check whether SUNRPC/GSS-related kernel functionality is present or enabled.
Confirm patch status against the referenced kernel stable commits.
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-50821 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
8Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Dec 30, 2025, 12:08 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.