LiveActive security incident?Get immediate response
CVE Record

CVE-2021-47507: nfsd: Fix nsfd startup race (again)

In the Linux kernel, the following vulnerability has been resolved: nfsd: Fix nsfd startup race (again) Commit bd5ae9288d64 ("nfsd: register pernet ops last, unregister first") has re-opened rpc_pipefs_event() race against nfsd_net_id registration (register_pernet_subsys()) which has been fixed by commit bb7ffbf29e76 ("nfsd: fix nsfd startup race triggering BUG_ON"). Restore the order of register_pernet_subsys() vs register_cld_notifier(). Add WARN_ON() to prevent a future regression. Crash info: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000012 CPU: 8 PID: 345 Comm: mount Not tainted 5.4.144-... #1 pc : rpc_pipefs_event+0x54/0x120 [nfsd] lr : rpc_pipefs_event+0x48/0x120 [nfsd] Call trace: rpc_pipefs_event+0x54/0x120 [nfsd] blocking_notifier_call_chain rpc_fill_super get_tree_keyed rpc_fs_get_tree vfs_get_tree do_mount ksys_mount __arm64_sys_mount el0_svc_handler el0_svc

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel NFS server startup race that can crash the kernel during mount-related startup handling. The public record does not provide CVSS scoring or evidence of active exploitation. Business urgency depends on whether affected Linux kernels are used on systems running or starting NFS server functionality.

Executive priority

Treat as a targeted stability risk for Linux NFS server infrastructure, not as confirmed active exploitation. Prioritize patch validation on production file-sharing, storage, and infrastructure hosts where kernel crashes would cause service disruption.

Technical view

The issue is in nfsd startup ordering around register_pernet_subsys(), register_cld_notifier(), and rpc_pipefs_event(). A prior ordering change reopened a race against nfsd_net_id registration, leading to a NULL pointer dereference in rpc_pipefs_event() and kernel crash. Stable kernel commits restore the registration order and add WARN_ON() regression protection.

Likely exposure

Likely exposure is Linux systems using affected kernel versions and nfsd-related startup paths. The source bundle names Linux kernel versions and stable commits, but does not provide distribution package mappings, exploit prerequisites, or complete environmental requirements.

Exploitation context

The bundle shows a crash trace triggered during mount processing and marks KEV as false. There is no cited evidence of active exploitation, public weaponization, remote reachability, privilege requirements, or attacker-controlled trigger conditions.

Researcher notes

Evidence is strongest for a kernel NULL pointer crash caused by startup race ordering in nfsd. The record lacks CVSS, CWE, exploitability details, and distro-specific fixed builds. Avoid assuming remote exploitability without additional vendor evidence.

Mitigation direction

  • Update to a vendor-supported kernel containing the referenced stable fixes.
  • Check Linux distribution advisories for backported package names and fixed versions.
  • Prioritize systems providing NFS server functionality or loading nfsd.
  • If updates are delayed, follow vendor guidance for temporary operational workarounds.

Validation and detection

  • Inventory Linux kernel versions against the affected versions in the CVE record.
  • Identify hosts where nfsd or NFS server functionality is enabled.
  • Confirm the deployed kernel includes one of the referenced stable fix commits or vendor backport.
  • Review kernel logs for rpc_pipefs_event or nfsd NULL pointer crash signatures.
Prepared
Confidence
medium
Sources
6

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-47507 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux8677e99150b0830d29cc1318b4cc559e176940bb, 7c7cb07d4affcf41749234fe9dc4d90cd3959e32, bd5ae9288d6451bd346a1b4a59d4fe7e62ba29b7, bd5ae9288d6451bd346a1b4a59d4fe7e62ba29b7, 4d41f65efeec0a6da6088341203c81e49ebfcd90unaffected
LinuxLinux5.12, 0, 5.4.165, 5.10.85, 5.15.8, 5.16affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.