linux-cve-announce - CVE-2025-40195: mount: handle NULL values in mnt_ns

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025111245-CVE-2025-40195-f91e@gregkh>
Date: Wed, 12 Nov 2025 17:00:58 -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-40195: mount: handle NULL values in mnt_ns_release()

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

mount: handle NULL values in mnt_ns_release()

When calling in listmount() mnt_ns_release() may be passed a NULL
pointer. Handle that case gracefully.

The Linux kernel CVE team has assigned CVE-2025-40195 to this issue.


Affected and fixed versions
===========================

	Fixed in 6.12.54 with commit 2d68f8a7379d9c61005e982600c61948d4d019bd
	Fixed in 6.17.4 with commit 99ae3e70a293834d0274c46a37120c71a24a4995
	Fixed in 6.18-rc1 with commit 6c7ca6a02f8f9549a438a08a23c6327580ecf3d6

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-40195
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/2d68f8a7379d9c61005e982600c61948d4d019bd
	https://git.kernel.org/stable/c/99ae3e70a293834d0274c46a37120c71a24a4995
	https://git.kernel.org/stable/c/6c7ca6a02f8f9549a438a08a23c6327580ecf3d6