From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795154251; b=qzLlhnjHRZr3fLvodKQNwFjFO5rf4aUUvPnGPwh494LLBA9AMQ8xld7GCGUrhVgIrWVP 6d1ZsSeh8VRdopvPdfyTacfWo4Qb4lV5uT1kjdB0Z+TSOzsSna7J1XGKl3iId0GffAD8w kEzzHYhVA8KZtLJAsh+8uGzft3SPS93HzqCkPrMvFYCY+UUqveXFuRmAuakOgtkzkOeez MSaziAuFePIvFarbXYuQQR03v1iLeTxCTCOgl8LCTTspjun2QeZ68ZMquozMStJ2Y+rYf 9l/wE21uAUy1LRkZPDjO8ggL0aUsqc4DBLkwE1CYrKH31DCGx90FU5q3TAs/4SUmJww== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154251; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=yWciOvgzIqNqsoisr7vHCng7WuvORFibkzRcVTB3jGY=; b=Ais0B119royabXyMu0g0CSxJqwKrtejWgbV7CsewmVPVmcMt2WuMfPlY92v8Qt6n1bUr 7ZIrkVkvNlR2ihaKQ93JJGfZ9oBvTJ91tZL9AbuzimFVW1q3uNpU0NObJIquy/gYFEOAl d4hcGWOtgTQaKaSGdd/ZgGRZov83HtsgYTBktUUBlOonc5n1wZxbXDJLbiibrOU2W7pRp HFXghNdemmB4iTrDakbLWx3Wikgfkkic3yKuCmxKf4rqJ/jIbPjFkhhSAIXgdkpnpue2l YxRdGX7jF781f92n1OWP3TWrv3BeMp9NCooYmZGeh1taGvIgIqfPr7Kora8Y/azaZMg== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=nkLY4UY3; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3F0F8606A33F for ; Fri, 20 Nov 2026 05:57:31 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=nkLY4UY3 Received: by smtp.kernel.org (Postfix) with ESMTPSA id 541E91F000C4; Fri, 20 Nov 2026 05:57:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154250; bh=yWciOvgzIqNqsoisr7vHCng7WuvORFibkzRcVTB3jGY=; h=From:To:Cc:Subject:Date:Reply-To; b=nkLY4UY3/kcM5ijtQ7sU8D0Si87RZA3xXntF6RKCmSwUKOUU5bBMD4z3cqo0TVaBx B6Sd+mYElCIY3s4UYaDylLcAZTB6V245FA1LAUdLnuRgunQgzoMNrnTYg9J8pU8GzP zqDo5mEyukIs1HEV9rMfVWhBW1trE/AQ6m8WQP1I= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99641: ovl: fail the mount if the casefold flag has changed Date: Fri, 20 Nov 2026 06:50:27 +0100 Message-ID: <2026112040-CVE-2026-99641-7ee7@gregkh> X-Mailer: git-send-email 2.56.1 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3402; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=CpxOq8bOoszHNtveX81fhxQOTXgDg7m7+1GlRAlbPfk=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/75dceSp+eyk3T7+Hx8xZjXrOP0vefdFrXbl53akHf mIKkq08HbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjCREzUMC3r3mZk1Py6f+iXq oePaK+IuR6c+E2WYH9lfv0N/6hWh0xyhfzWdptyz1dc/CgA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: ovl: fail the mount if the casefold flag has changed An unprivileged user in a user namespace can repeatedly trigger a kernel warning with their own overlay mounts. They do so by changing the casefold flag of the topmost layer's empty root, the top directory of that layer, after the layers are set and before the mount is created. The casefold flag of a directory makes name lookups in that directory case-insensitive. All layers of an overlay must agree on casefolding. ovl_mount_dir_check() reads the casefold flag of a layer root when fsconfig() sets that layer, and saves the result in ofs->casefold. The mount is created later, by another fsconfig() call with FSCONFIG_CMD_CREATE. The casefold flag of an empty directory can be changed. The casefold flag of the overlay root must match ofs->casefold. ovl_get_root() copies the flag from the topmost layer root, as it is when the mount is created. On a mismatch, ovl_get_root() only does a WARN_ON(), and the mount continues. The check is not a WARN_ON_ONCE(), so each such mount warns again. An unprivileged user needs CONFIG_UNICODE, and a tmpfs mounted with the casefold option in their namespace. Reproduced by changing the casefold flag of the empty upper directory after the layers were set and before FSCONFIG_CMD_CREATE, with tmpfs and ext4 layers, and as uid 1000 in a user namespace. Fix this by replacing the WARN_ON() with a check that fails the mount with -EINVAL. The Linux kernel CVE team has assigned CVE-2026-99641 to this issue. Affected and fixed versions =========================== Issue introduced in 6.18 with commit f9377faaeae0473ea45f2b6d3ff758e192f3f01d and fixed in 6.18.64 with commit f182e7bc11c401d09f890ee1a3ec359670e1e308 Issue introduced in 6.18 with commit f9377faaeae0473ea45f2b6d3ff758e192f3f01d and fixed in 7.3.5 with commit 549fb7c77951ad9ddfed05ce1776f497538ad13e Issue introduced in 6.18 with commit f9377faaeae0473ea45f2b6d3ff758e192f3f01d and fixed in 7.4-rc2 with commit c782fc8ada811569811c0fdea5c3412511be95d0 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-2026-99641 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/overlayfs/super.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/f182e7bc11c401d09f890ee1a3ec359670e1e308 https://git.kernel.org/stable/c/549fb7c77951ad9ddfed05ce1776f497538ad13e https://git.kernel.org/stable/c/c782fc8ada811569811c0fdea5c3412511be95d0