[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025072556-CVE-2025-38430-dafd@gregkh>
Date: Fri, 25 Jul 2025 16:17:03 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38430: nfsd: nfsd4_spo_must_allow() must check this is a v4 compound request
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
nfsd: nfsd4_spo_must_allow() must check this is a v4 compound request
If the request being processed is not a v4 compound request, then
examining the cstate can have undefined results.
This patch adds a check that the rpc procedure being executed
(rq_procinfo) is the NFSPROC4_COMPOUND procedure.
The Linux kernel CVE team has assigned CVE-2025-38430 to this issue.
Affected and fixed versions
===========================
Fixed in 5.4.295 with commit bf78a2706ce975981eb5167f2d3b609eb5d24c19
Fixed in 5.10.239 with commit b1d0323a09a29f81572c7391e0d80d78724729c9
Fixed in 5.15.186 with commit 425efc6b3292a3c79bfee4a1661cf043dcd9cf2f
Fixed in 6.1.142 with commit 64a723b0281ecaa59d31aad73ef8e408a84cb603
Fixed in 6.6.95 with commit e7e943ddd1c6731812357a28e7954ade3a7d8517
Fixed in 6.12.35 with commit 7a75a956692aa64211a9e95781af1ec461642de4
Fixed in 6.15.4 with commit 2c54bd5a380ebf646fb9efbc4ae782ff3a83a5af
Fixed in 6.16-rc1 with commit 1244f0b2c3cecd3f349a877006e67c9492b41807
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-38430
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/nfs4proc.c
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/bf78a2706ce975981eb5167f2d3b609eb5d24c19
https://git.kernel.org/stable/c/b1d0323a09a29f81572c7391e0d80d78724729c9
https://git.kernel.org/stable/c/425efc6b3292a3c79bfee4a1661cf043dcd9cf2f
https://git.kernel.org/stable/c/64a723b0281ecaa59d31aad73ef8e408a84cb603
https://git.kernel.org/stable/c/e7e943ddd1c6731812357a28e7954ade3a7d8517
https://git.kernel.org/stable/c/7a75a956692aa64211a9e95781af1ec461642de4
https://git.kernel.org/stable/c/2c54bd5a380ebf646fb9efbc4ae782ff3a83a5af
https://git.kernel.org/stable/c/1244f0b2c3cecd3f349a877006e67c9492b41807
Powered by blists - more mailing lists