In the Linux kernel, the following vulnerability has been resolved:
NFSD: Fix nfsd4_encode_fattr4() crasher
Ensure that args.acl is initialized early. It is used in an
unconditional call to kfree() on the way out of
nfsd4_encode_fattr4().
Security readout for executives and security teams
Plain-English summary
A Linux NFS server flaw can crash affected kernels because cleanup may free an uninitialized ACL pointer. This can disrupt systems providing NFS services. The supplied evidence does not demonstrate data theft, data modification, or active exploitation, despite the 9.8 CVSS rating.
Executive priority
Treat exposed or business-critical NFS servers as urgent patching candidates because a kernel crash can interrupt shared storage and dependent operations. Rapidly inventory NFSD systems and obtain vendor-confirmed updates. Do not classify every Linux host as affected without package-level validation.
Technical view
In nfsd4_encode_fattr4(), args.acl was not initialized early enough. An error path unconditionally passes it to kfree(), potentially causing a kernel crash. Referenced Linux stable commits correct the initialization. The source bundle does not establish a practical impact beyond the documented crasher.
Likely exposure
Candidates are Linux systems running affected kernel builds with NFSD functionality in use, especially network-reachable NFS servers. The bundle's flattened version data is ambiguous, so affected status should not be decided from upstream version labels alone; confirm distribution or appliance package status.
Exploitation context
CISA KEV status is false, and no supplied source reports active exploitation. That does not prove exploitation is absent. The network CVSS vector indicates remote reachability, but the bundle provides no exploit prerequisites, observed attacks, or evidence supporting confidentiality and integrity impact.
Researcher notes
The documented defect is an uninitialized args.acl reaching unconditional kfree() during nfsd4_encode_fattr4() cleanup. Source evidence supports a crash condition, but not the CVSS confidentiality or integrity claims. Exact affected ranges and exploitability conditions remain insufficiently detailed in the supplied bundle.
Mitigation direction
Obtain exact fixed kernel package information from the relevant distribution or appliance vendor.
Install a vendor-supported update incorporating the applicable referenced Linux stable fix.
If no update is available, request a supported temporary mitigation from the vendor; none is named here.
Validation and detection
Inventory running kernel packages and identify systems providing NFSD services.
Compare each package build with the vendor's affected and fixed version guidance.
Confirm the deployed kernel includes an applicable referenced fix or vendor backport.
After updating, verify systems boot normally and required NFS services remain 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-36958 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.