CVE-2021-47179: NFSv4: Fix a NULL pointer dereference in pnfs_mark_matching_lsegs_return()
In the Linux kernel, the following vulnerability has been resolved:
NFSv4: Fix a NULL pointer dereference in pnfs_mark_matching_lsegs_return()
Commit de144ff4234f changes _pnfs_return_layout() to call
pnfs_mark_matching_lsegs_return() passing NULL as the struct
pnfs_layout_range argument. Unfortunately,
pnfs_mark_matching_lsegs_return() doesn't check if we have a value here
before dereferencing it, causing an oops.
I'm able to hit this crash consistently when running connectathon basic
tests on NFS v4.1/v4.2 against Ontap.
Security readout for executives and security teams
Plain-English summary
CVE-2021-47179 is a Linux kernel NFSv4 flaw that can trigger a kernel oops from a NULL pointer dereference. The report describes consistent crashes during NFS v4.1/v4.2 connectathon basic tests against Ontap. The practical concern is service availability for Linux systems using affected NFSv4 client code.
Executive priority
Schedule remediation through normal kernel patch cycles, with higher priority for business-critical NFS clients. Escalate if internal evidence shows crashes, NFS instability, or exposure on critical file-service paths.
Technical view
The bug is in pnfs_mark_matching_lsegs_return(). A prior change made _pnfs_return_layout() pass a NULL pnfs_layout_range pointer, but the callee dereferenced it without checking. Linux stable commits add the missing handling. Sources do not provide CVSS, CWE, exploitability, or broad attack prerequisites.
Likely exposure
Likely exposure is Linux systems using NFSv4, especially v4.1/v4.2 pNFS layouts, on kernel builds containing the faulty change before the stable fixes. The provided data names Linux only and does not identify distributions or non-Linux products.
Exploitation context
No CISA KEV listing is provided, and the bundle does not cite active exploitation. Evidence is limited to reproducible crashes in testing against Ontap, so treat this as an availability risk until vendor or distribution guidance says otherwise.
Researcher notes
The source bundle supports a NULL dereference in Linux NFSv4 pNFS layout-return handling. It does not establish remote exploitability, privilege requirements, exploit availability, or data compromise. Analysis should stay focused on crash reproduction conditions and fixed kernel lineage.
Mitigation direction
Apply Linux kernel stable updates containing the referenced fixes.
Check your distribution security advisory for the corrected package version.
Prioritize NFSv4 client systems and systems using pNFS layouts.
If immediate patching is delayed, consult vendor guidance for safe NFSv4 workarounds.
Validation and detection
Inventory Linux hosts that mount or rely on NFSv4.1 or NFSv4.2.
Compare running kernel builds against vendor fixed versions or referenced stable commits.
Review logs for kernel oops or NFSv4/pNFS layout-return crashes.
Confirm patched systems no longer run affected kernel builds.
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-47179 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.