| 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
| ||
|
Message-ID: <2025073029-CVE-2025-38498-e3ab@gregkh> Date: Wed, 30 Jul 2025 08:03:30 +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-38498: do_change_type(): refuse to operate on unmounted/not ours mounts From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: do_change_type(): refuse to operate on unmounted/not ours mounts Ensure that propagation settings can only be changed for mounts located in the caller's mount namespace. This change aligns permission checking with the rest of mount(2). The Linux kernel CVE team has assigned CVE-2025-38498 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.15 with commit 07b20889e3052c7e77d6a6a54e7e83446eb1ba84 and fixed in 5.4.295 with commit 787937c4e373f1722c4343e5a5a4eb0f8543e589 Issue introduced in 2.6.15 with commit 07b20889e3052c7e77d6a6a54e7e83446eb1ba84 and fixed in 5.10.239 with commit c7d11fdf8e5db5f34a6c062c7e6ba3a0971879d2 Issue introduced in 2.6.15 with commit 07b20889e3052c7e77d6a6a54e7e83446eb1ba84 and fixed in 5.15.186 with commit 432a171d60056489270c462e651e6c3a13f855b1 Issue introduced in 2.6.15 with commit 07b20889e3052c7e77d6a6a54e7e83446eb1ba84 and fixed in 6.1.142 with commit 064014f7812744451d5d0592f3d2bcd727f2ee93 Issue introduced in 2.6.15 with commit 07b20889e3052c7e77d6a6a54e7e83446eb1ba84 and fixed in 6.6.94 with commit 4f091ad0862b02dc42a19a120b7048de848561f8 Issue introduced in 2.6.15 with commit 07b20889e3052c7e77d6a6a54e7e83446eb1ba84 and fixed in 6.12.34 with commit 9c1ddfeb662b668fff69c5f1cfdd9f5d23d55d23 Issue introduced in 2.6.15 with commit 07b20889e3052c7e77d6a6a54e7e83446eb1ba84 and fixed in 6.15.3 with commit 19554c79a2095ddde850906a067915c1ef3a4114 Issue introduced in 2.6.15 with commit 07b20889e3052c7e77d6a6a54e7e83446eb1ba84 and fixed in 6.16 with commit 12f147ddd6de7382dad54812e65f3f08d05809fc 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-38498 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/787937c4e373f1722c4343e5a5a4eb0f8543e589 https://git.kernel.org/stable/c/c7d11fdf8e5db5f34a6c062c7e6ba3a0971879d2 https://git.kernel.org/stable/c/432a171d60056489270c462e651e6c3a13f855b1 https://git.kernel.org/stable/c/064014f7812744451d5d0592f3d2bcd727f2ee93 https://git.kernel.org/stable/c/4f091ad0862b02dc42a19a120b7048de848561f8 https://git.kernel.org/stable/c/9c1ddfeb662b668fff69c5f1cfdd9f5d23d55d23 https://git.kernel.org/stable/c/19554c79a2095ddde850906a067915c1ef3a4114 https://git.kernel.org/stable/c/12f147ddd6de7382dad54812e65f3f08d05809fc
Powered by blists - more mailing lists