CVE-2024-56558: nfsd: make sure exp active before svc_export_show
In the Linux kernel, the following vulnerability has been resolved:
nfsd: make sure exp active before svc_export_show
The function `e_show` was called with protection from RCU. This only
ensures that `exp` will not be freed. Therefore, the reference count for
`exp` can drop to zero, which will trigger a refcount use-after-free
warning when `exp_get` is called. To resolve this issue, use
`cache_get_rcu` to ensure that `exp` remains active.
------------[ cut here ]------------
refcount_t: addition on 0; use-after-free.
WARNING: CPU: 3 PID: 819 at lib/refcount.c:25
refcount_warn_saturate+0xb1/0x120
CPU: 3 UID: 0 PID: 819 Comm: cat Not tainted 6.12.0-rc3+ #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
1.16.1-2.fc37 04/01/2014
RIP: 0010:refcount_warn_saturate+0xb1/0x120
...
Call Trace:
<TASK>
e_show+0x20b/0x230 [nfsd]
seq_read_iter+0x589/0x770
seq_read+0x1e5/0x270
vfs_read+0x125/0x530
ksys_read+0xc1/0x160
do_syscall_64+0x5f/0x170
entry_SYSCALL_64_after_hwframe+0x76/0x7e
Security readout for executives and security teams
Plain-English summary
A Linux NFS server kernel component can mishandle the lifetime of an export object during status display. A local, low-privileged user may trigger a use-after-free warning. The supplied record rates potential confidentiality, integrity, and availability impact as high, but provides no evidence of successful compromise or active exploitation.
Executive priority
Prioritize expedited remediation on NFS servers shared by users or untrusted workloads. Treat isolated systems without nfsd as lower urgency after confirming component usage. There is high theoretical impact but no supplied evidence of exploitation, so this warrants controlled patching rather than emergency incident response by itself.
Technical view
Within nfsd, e_show relied on RCU to prevent exp from being freed, but RCU did not ensure its reference count remained above zero. A subsequent exp_get could add a reference to an inactive object, producing a refcount use-after-free warning. The kernel fix uses cache_get_rcu to keep the export active.
Likely exposure
Exposure is most relevant to affected Linux systems using the nfsd component, particularly multi-user or otherwise locally accessible hosts. The supplied affected-version data is ambiguous, so vulnerability managers should confirm fixed kernel builds through their distribution rather than relying solely on upstream version numbers.
Exploitation context
The CVSS 3.1 vector is 7.8 and requires local access with low privileges; no user interaction is required. The bundle reports no KEV listing, and none of the supplied sources documents active exploitation, a public exploit, remote reachability, or demonstrated data compromise.
Researcher notes
The reproduced trace demonstrates a refcount addition on zero in e_show, classified as CWE-416. It does not establish reliable memory corruption, privilege escalation, or code execution. Multiple Linux stable commits indicate backports, while Debian LTS advisories provide downstream remediation context. Exact affected and fixed release boundaries remain unclear in the supplied version data.
Mitigation direction
Install a distribution-supported kernel update containing the CVE-2024-56558 fix.
Reboot into the updated kernel after following the distribution's deployment guidance.
Disable nfsd where NFS server functionality is unnecessary, subject to operational approval.
Restrict local account and workload access until affected systems are updated.
Validation and detection
Inventory running kernel builds and identify systems providing NFS server functionality.
Confirm each distribution package includes its vendor's CVE-2024-56558 correction.
Verify systems booted into the corrected kernel after maintenance.
Review kernel logs for refcount use-after-free warnings involving e_show or nfsd.
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.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
2CVSS vectors
3Timeline events
2ADP providers
10Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.