CVE-2024-46697: nfsd: ensure that nfsd4_fattr_args.context is zeroed out
In the Linux kernel, the following vulnerability has been resolved:
nfsd: ensure that nfsd4_fattr_args.context is zeroed out
If nfsd4_encode_fattr4 ends up doing a "goto out" before we get to
checking for the security label, then args.context will be set to
uninitialized junk on the stack, which we'll then try to free.
Initialize it early.
Security readout for executives and security teams
Plain-English summary
A Linux NFS server can follow an error path that treats uninitialized memory as a valid security context and attempts to free it. This memory-safety failure could disrupt exposed NFS services and may have broader consequences, although the supplied sources do not demonstrate a specific impact chain.
Executive priority
Treat this as urgent on reachable NFS servers because the supplied rating is CVSS 9.8 and the vulnerable path is network-facing. Prioritize inventory and supported kernel updates, while recognizing that real-world exploitation has not been established by the supplied evidence.
Technical view
Within Linux nfsd, nfsd4_encode_fattr4 can exit before security-label handling. Without early initialization, nfsd4_fattr_args.context may contain uninitialized stack data and later be freed as valid. The referenced stable commits initialize the context early. The supplied sources do not establish demonstrated code execution or data compromise.
Likely exposure
Exposure is concentrated on Linux systems providing NFS through nfsd, particularly builds represented by the affected 6.7, 6.10.8, and 6.11 entries. The supplied version data is ambiguous and includes “0,” so distribution backports and advisories must determine actual exposure.
Exploitation context
The supplied CVSS vector describes network access, low complexity, no privileges, and no user interaction. However, this CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation, a public proof of concept, or reliable remote code execution.
Researcher notes
The central primitive is an invalid free caused by an uninitialized context pointer on an early exit path. The fix initializes that field before possible exits. Version boundaries in the supplied affected data are insufficiently clear; validate against vendor package advisories and commit backports rather than version strings alone.
Mitigation direction
Identify Linux systems running nfsd and prioritize NFS servers reachable by untrusted clients.
Apply a vendor-supported kernel update containing the applicable referenced stable fix.
Follow distribution guidance because kernel fixes may be backported without matching upstream version numbers.
If updating is delayed, restrict NFS access and disable unnecessary nfsd services.
Reboot into the updated kernel according to vendor instructions.
Validation and detection
Confirm whether nfsd is enabled and identify hosts exposing NFS to untrusted networks.
Record each server’s running kernel build and distribution package revision.
Compare builds with distribution advisories and backport records for CVE-2024-46697.
Verify the referenced initialization change, or its vendor-equivalent backport, is present.
After remediation, confirm the updated kernel is running and NFS remains healthy.
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-2024-46697 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.
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.