[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025041654-CVE-2025-22026-f6be@gregkh>
Date: Wed, 16 Apr 2025 16:11:57 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2025-22026: nfsd: don't ignore the return code of svc_proc_register()
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
nfsd: don't ignore the return code of svc_proc_register()
Currently, nfsd_proc_stat_init() ignores the return value of
svc_proc_register(). If the procfile creation fails, then the kernel
will WARN when it tries to remove the entry later.
Fix nfsd_proc_stat_init() to return the same type of pointer as
svc_proc_register(), and fix up nfsd_net_init() to check that and fail
the nfsd_net construction if it occurs.
svc_proc_register() can fail if the dentry can't be allocated, or if an
identical dentry already exists. The second case is pretty unlikely in
the nfsd_net construction codepath, so if this happens, return -ENOMEM.
The Linux kernel CVE team has assigned CVE-2025-22026 to this issue.
Affected and fixed versions
===========================
Fixed in 6.14.2 with commit 9d9456185fd5f1891c74354ee297f19538141ead
Fixed in 6.15-rc1 with commit 930b64ca0c511521f0abdd1d57ce52b2a6e3476b
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2025-22026
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
fs/nfsd/nfsctl.c
fs/nfsd/stats.c
fs/nfsd/stats.h
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/9d9456185fd5f1891c74354ee297f19538141ead
https://git.kernel.org/stable/c/930b64ca0c511521f0abdd1d57ce52b2a6e3476b
Powered by blists - more mailing lists