[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025111247-CVE-2025-40203-c83b@gregkh>
Date: Wed, 12 Nov 2025 17:01:06 -0500
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-40203: listmount: don't call path_put() under namespace semaphore
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
listmount: don't call path_put() under namespace semaphore
Massage listmount() and make sure we don't call path_put() under the
namespace semaphore. If we put the last reference we're fscked.
The Linux kernel CVE team has assigned CVE-2025-40203 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.8 with commit b4c2bea8ceaa50cd42a8f73667389d801a3ecf2d and fixed in 6.12.54 with commit 659874b7ee4976ad9ce476e07fd36bc67b3537f1
Issue introduced in 6.8 with commit b4c2bea8ceaa50cd42a8f73667389d801a3ecf2d and fixed in 6.17.4 with commit 9c80da26fda2fdcaac7f92b5908875b3108830ff
Issue introduced in 6.8 with commit b4c2bea8ceaa50cd42a8f73667389d801a3ecf2d and fixed in 6.18-rc1 with commit c1f86d0ac322c7e77f6f8dbd216c65d39358ffc0
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-40203
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/namespace.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/659874b7ee4976ad9ce476e07fd36bc67b3537f1
https://git.kernel.org/stable/c/9c80da26fda2fdcaac7f92b5908875b3108830ff
https://git.kernel.org/stable/c/c1f86d0ac322c7e77f6f8dbd216c65d39358ffc0
Powered by blists - more mailing lists