CVE-2022-50072: NFSv4/pnfs: Fix a use-after-free bug in open
In the Linux kernel, the following vulnerability has been resolved:
NFSv4/pnfs: Fix a use-after-free bug in open
If someone cancels the open RPC call, then we must not try to free
either the open slot or the layoutget operation arguments, since they
are likely still in use by the hung RPC call.
Security readout for executives and security teams
Plain-English summary
A memory-safety flaw in the Linux kernel’s NFSv4/pNFS open handling can leave an ongoing RPC using memory that has already been freed. The supplied CVSS assessment indicates a low-privileged local attacker could potentially compromise confidentiality, integrity, and availability, but the sources do not document a demonstrated outcome.
Executive priority
Treat this as a high-priority kernel maintenance issue, especially for shared Linux hosts using NFSv4/pNFS. It is not supported as an emergency internet-wide threat because the supplied assessment requires local access and provides no active-exploitation evidence. Remediate through normal accelerated patching and verify vendor backports rather than relying solely on upstream version strings.
Technical view
When an NFS open RPC is cancelled while still hung, the kernel may prematurely free the open slot or layoutget arguments. The outstanding RPC can subsequently access those objects, creating a use-after-free condition. CVSS 3.1 scores it 7.8 with local access, low complexity, low privileges, no user interaction, and high potential impact.
Likely exposure
Exposure is limited to Linux systems running a vulnerable kernel and exercising the affected NFSv4/pNFS open path. The supplied version data mixes release numbers and commit identifiers and is insufficient for reliable distribution-package mapping. Systems using vendor-backported kernels require confirmation through their distributor’s advisory or package metadata.
Exploitation context
The record is not listed as CISA KEV, and the supplied sources provide no evidence of active exploitation or a public exploit. That does not prove exploitation is absent. The CVSS vector describes local, low-privileged access rather than unauthenticated network exploitation, while the underlying condition depends on cancellation of an outstanding open RPC.
Researcher notes
The core issue is object-lifetime handling across asynchronous RPC cancellation: cleanup must not release the open slot or layoutget arguments while a hung RPC may retain references. The supplied record does not identify a CWE, proven exploitation primitive, affected distributions, or observed crash or code-execution behavior. Version interpretation should therefore remain conservative.
Mitigation direction
Upgrade to a vendor-supported kernel confirmed to contain the applicable stable fix or backport.
Consult the Linux distribution’s advisory because package versions may not match upstream kernel numbering.
Prioritize remediation on multi-user or workload-hosting systems that actively use NFSv4/pNFS.
If immediate updating is impossible, obtain vendor-approved temporary mitigation guidance; none is specified in the supplied sources.
Validation and detection
Inventory running kernel and distribution package versions across Linux systems.
Identify hosts mounting or configured to use NFSv4 with pNFS capabilities.
Map each vendor kernel package to its advisory and confirmed backport status.
After updating and rebooting, confirm the fixed kernel is running.
Review kernel logs for relevant NFS failures or crashes without treating their absence as proof of safety.
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-50072 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.
1CVSS vectors
3Timeline events
0ADP providers
7Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.