CVE-2021-47322: NFSv4: Fix an Oops in pnfs_mark_request_commit() when doing O_DIRECT
In the Linux kernel, the following vulnerability has been resolved:
NFSv4: Fix an Oops in pnfs_mark_request_commit() when doing O_DIRECT
Fix an Oopsable condition in pnfs_mark_request_commit() when we're
putting a set of writes on the commit list to reschedule them after a
failed pNFS attempt.
Security readout for executives and security teams
Plain-English summary
CVE-2021-47322 is a Linux kernel NFSv4 defect that can trigger a kernel Oops during direct I/O after a failed pNFS write attempt. The business concern is service instability on affected Linux systems using this storage path, not confirmed data theft or remote compromise.
Executive priority
Schedule remediation through normal kernel maintenance, with higher priority for production systems dependent on NFSv4/pNFS storage. There is no source evidence of active exploitation, but kernel Oops conditions can disrupt critical services.
Technical view
The issue is in pnfs_mark_request_commit(), where NFSv4/pNFS write requests are moved to a commit list for rescheduling after failed pNFS handling. The CVE record says this path was Oopsable when doing O_DIRECT. Linux stable commit references are provided as fixes.
Likely exposure
Exposure appears limited to affected Linux kernel versions using NFSv4/pNFS and O_DIRECT write behavior. The source lists affected Linux versions including 5.7, 5.10.52, 5.12.19, 5.13.4, and 5.14, but packaging and backports require vendor confirmation.
Exploitation context
The source bundle does not identify active exploitation, public exploit activity, CVSS scoring, or a CWE. CISA KEV status is false. Treat this as a kernel availability and reliability issue unless additional vendor evidence expands the impact.
Researcher notes
Evidence is narrow: the CVE describes an Oopsable NFSv4/pNFS direct I/O path and provides kernel stable fix links. No CVSS, CWE, exploit status, or detailed impact narrative is included, so exposure analysis should be confirmed against distribution-specific advisories and deployed workload behavior.
Mitigation direction
Apply a vendor-supported Linux kernel update containing the referenced stable fixes.
Check distribution advisories for backported fixes before relying on upstream version numbers.
Prioritize systems using NFSv4, pNFS, and direct I/O workloads.
If no update is available, ask the vendor for supported mitigation guidance.
Validation and detection
Inventory Linux kernel versions across NFS clients and servers.
Identify workloads using NFSv4 or pNFS with direct I/O.
Confirm whether installed vendor kernels include the referenced stable commits.
Review kernel logs for Oops events referencing pnfs_mark_request_commit or O_DIRECT.
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-2021-47322 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.