CVE-2022-50006: NFSv4.2 fix problems with __nfs42_ssc_open
In the Linux kernel, the following vulnerability has been resolved:
NFSv4.2 fix problems with __nfs42_ssc_open
A destination server while doing a COPY shouldn't accept using the
passed in filehandle if its not a regular filehandle.
If alloc_file_pseudo() has failed, we need to decrement a reference
on the newly created inode, otherwise it leaks.
Security readout for executives and security teams
Plain-English summary
CVE-2022-50006 is a Linux kernel NFSv4.2 issue involving server-side COPY handling and cleanup after an internal file allocation failure. The public record does not provide a CVSS score, CWE, exploitability assessment, or confirmed impact. Treat it as a kernel maintenance exposure, especially for systems using NFSv4.2 features.
Executive priority
Medium operational priority until vendor severity is clarified. Patch during normal kernel maintenance unless the organization has heavy NFSv4.2 use or exposed NFS services, in which case accelerate validation and remediation planning.
Technical view
The issue was resolved in Linux kernel NFSv4.2 code around __nfs42_ssc_open. The fix prevents a destination server during COPY from accepting a passed filehandle when it is not a regular filehandle, and corrects an inode reference leak if alloc_file_pseudo() fails.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions with NFSv4.2 functionality in use. The bundle lists Linux as affected but does not provide distribution package names, enabled-by-default status, or precise environmental prerequisites.
Exploitation context
No active exploitation is supported by the supplied sources. The CVE is not listed as KEV in the bundle, and no cited source describes public exploit activity, exploit code, or attacker requirements.
Researcher notes
Evidence is limited to the CVE record and upstream stable kernel references. The record describes correctness and reference-management fixes but does not establish confidentiality, integrity, availability impact, privilege boundary, or remote exploitability.
Mitigation direction
Check your Linux distribution advisory for CVE-2022-50006 coverage.
Apply kernel updates containing the referenced upstream stable fixes.
Prioritize systems providing or relying on NFSv4.2 services.
Track vendor backports instead of relying only on upstream version numbers.
Validation and detection
Inventory Linux kernel versions on NFS-capable systems.
Confirm whether NFSv4.2 is enabled or used in production.
Verify installed kernel packages include the vendor fix for CVE-2022-50006.
Review change records against the referenced upstream 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-50006 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
5Source 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.
Jun 18, 2025, 11:01 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.