CVE-2026-23297: nfsd: Fix cred ref leak in nfsd_nl_threads_set_doit().
In the Linux kernel, the following vulnerability has been resolved:
nfsd: Fix cred ref leak in nfsd_nl_threads_set_doit().
syzbot reported memory leak of struct cred. [0]
nfsd_nl_threads_set_doit() passes get_current_cred() to
nfsd_svc(), but put_cred() is not called after that.
The cred is finally passed down to _svc_xprt_create(),
which calls get_cred() with the cred for struct svc_xprt.
The ownership of the refcount by get_current_cred() is not
transferred to anywhere and is just leaked.
nfsd_svc() is also called from write_threads(), but it does
not bump file->f_cred there.
nfsd_nl_threads_set_doit() is called from sendmsg() and
current->cred does not go away.
Let's use current_cred() in nfsd_nl_threads_set_doit().
[0]:
BUG: memory leak
unreferenced object 0xffff888108b89480 (size 184):
comm "syz-executor", pid 5994, jiffies 4294943386
hex dump (first 32 bytes):
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace (crc 369454a7):
kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
slab_post_alloc_hook mm/slub.c:4958 [inline]
slab_alloc_node mm/slub.c:5263 [inline]
kmem_cache_alloc_noprof+0x412/0x580 mm/slub.c:5270
prepare_creds+0x22/0x600 kernel/cred.c:185
copy_creds+0x44/0x290 kernel/cred.c:286
copy_process+0x7a7/0x2870 kernel/fork.c:2086
kernel_clone+0xac/0x6e0 kernel/fork.c:2651
__do_sys_clone+0x7f/0xb0 kernel/fork.c:2792
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xa4/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Security readout for executives and security teams
Plain-English summary
CVE-2026-23297 is a Linux kernel NFS server bug where a credential reference is leaked instead of released. Over repeated triggering, this can waste kernel memory and may affect system stability. The source bundle does not provide CVSS, real-world exploitation, or full distribution package status.
Executive priority
Schedule remediation through normal kernel patching, with higher priority for NFS server infrastructure. No active exploitation is evidenced in the supplied sources, but kernel memory leaks can still create availability risk on shared or critical systems.
Technical view
The issue is in nfsd_nl_threads_set_doit(), which passed get_current_cred() into nfsd_svc() without a matching put_cred(). The leaked struct cred reference was reported by syzbot. The fix changes the path to use current_cred(), avoiding an unowned reference increment.
Likely exposure
Exposure is most likely on Linux systems running affected kernel versions where kernel NFS server code is present and the nfsd thread-setting path can be reached. Distribution backports may change version-based conclusions, so package-level advisory checks are necessary.
Exploitation context
The provided sources show a syzbot memory leak report and stable kernel fixes. They do not show active exploitation, KEV listing, public exploit availability, or confirmed remote exploitation. Treat this primarily as a potential kernel resource-exhaustion stability issue based on available evidence.
Researcher notes
The source identifies a credential reference leak, not a privilege escalation or data disclosure. Access prerequisites are not fully described in the bundle. Analysis should avoid assuming remote reachability and should focus on code-path reachability, vendor backports, and operational impact.
Mitigation direction
Update to a Linux kernel containing the referenced stable fixes or equivalent vendor backport.
Check distribution advisories for package names, fixed builds, and support status.
Prioritize affected systems that run or manage kernel NFS server services.
Track vendor guidance if immediate patching is not available.
Validation and detection
Inventory Linux kernel versions across NFS server hosts.
Confirm whether vendor kernels include backports for CVE-2026-23297.
Verify the relevant stable commit or equivalent patch is present.
Review kernel and NFS service logs for unexplained memory pressure.
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-2026-23297 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.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Mar 25, 2026, 10:26 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.