From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7BD7B33DEC0 for ; Sat, 22 Aug 2026 15:33:39 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787412820; cv=none; b=GhnB+Y6FEoBMskE3FdAS3b4H9YdqbphJUq4C00PvvkHT9oqTst1NLjzURqTbXiGnc9bbgRo77DMN1R3aZLBpBfpiia6u+PfWSV/fyJ0BqUNtqSXppsADv16j53croHvv2fJIpkhDrTV/fYaPFqJc5Y6JH3d0bfwgkA3DZDKkycA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787412820; c=relaxed/simple; bh=8Zodh2WjdXlbZPJFoC/zP3MWQaw00b6+x8KgTrW5nKU=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=KAgjgFPLTHHl1GkD5gX5GOeLSBtL6hl1wDDrDb6tdVDJlFdbfYpnPuR3a3ETNfnMy0i18WB71oHY6kawKBpE0ptm3pHjnGg2zpzUvPHB/F7Sdzijb0ZTrRRHuyR43wEzqchtJ2JIMijyUaBNhYbC8U6R7CDBoAcydhpqdMvvjAc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=V5pW+gvu; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="V5pW+gvu" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 74CA21F000E9; Sat, 22 Aug 2026 15:33:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1787412819; bh=JOwSRDeyQCJ0SqiiYpILFnnS5lU6Mf5wp1Yx0aWgHtM=; h=From:To:Cc:Subject:Date:Reply-To; b=V5pW+gvuexrYO6G23lNRTFtQKW6k+mS9iu+9bN2GYpGI5J9kKs38QlZhwosWuSJbs BDJMmOKrFeHdd7cqZIQdE1WN3xSG89A8HhK9h5VMwZu3/FVtwwk/chl0CFGSwG85HT vN7Tp0MWUyl8Ogo3fKuBebwVttF7k23bsp/wJk6c= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-74595: fscrypt: use the mount idmap for the owner check in fscrypt_ioctl_set_policy() Date: Sat, 22 Aug 2026 17:31:19 +0200 Message-ID: <2026082214-CVE-2026-74595-9491@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2983; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=iVw2cBCtsYChZljO5utNMLH8DKCNGEWb4WzOXogDgNA=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmdBw7Zf9i4mVPi1lnTIz/XL33Dtjfgnr7XtFsGa8zaX 6ldPPpHoCOWhUGQiUFWTJHlyzaeo/srDil6GdqehpnDygQyhIGLUwAmYhXCML/YIi7XdfXcbhF5 /UgpP425Yk52MQzzg3wFedjvOckcnG5wd6/s2/R9fFo2AA== 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: fscrypt: use the mount idmap for the owner check in fscrypt_ioctl_set_policy() fscrypt_ioctl_set_policy() calls inode_owner_or_capable() with &nop_mnt_idmap before allowing an encryption policy to be set, instead of the idmap of the mount the ioctl was issued on. fscrypt is used by filesystems that support idmapped mounts (e.g. ext4, f2fs), so on such a mount this compares the caller's fsuid against the unmapped on-disk owner rather than the mapped owner: the actual owner can be wrongly denied with -EACCES and an unrelated caller wrongly allowed. Use file_mnt_idmap(filp) instead. The Linux kernel CVE team has assigned CVE-2026-74595 to this issue. Affected and fixed versions =========================== Issue introduced in 5.12 with commit 14f3db5542e62bcf6fe088a09760ac52d55306c5 and fixed in 6.6.152 with commit 33b7e810ce09955aa02f3b632455cf5e7ac990a9 Issue introduced in 5.12 with commit 14f3db5542e62bcf6fe088a09760ac52d55306c5 and fixed in 6.12.104 with commit 6a67c460b12315033268dce597546984fe5739e7 Issue introduced in 5.12 with commit 14f3db5542e62bcf6fe088a09760ac52d55306c5 and fixed in 6.18.45 with commit 653e888a24c87b8bbeab44d7e558a1c1a3641088 Issue introduced in 5.12 with commit 14f3db5542e62bcf6fe088a09760ac52d55306c5 and fixed in 7.1.9 with commit 98516ba8b817f34e86bdd7a5b7a383cff75c3ddf Issue introduced in 5.12 with commit 14f3db5542e62bcf6fe088a09760ac52d55306c5 and fixed in 7.2 with commit cf6c993c0feca7984797e634deba3c80342e199a 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-74595 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/crypto/policy.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/33b7e810ce09955aa02f3b632455cf5e7ac990a9 https://git.kernel.org/stable/c/6a67c460b12315033268dce597546984fe5739e7 https://git.kernel.org/stable/c/653e888a24c87b8bbeab44d7e558a1c1a3641088 https://git.kernel.org/stable/c/98516ba8b817f34e86bdd7a5b7a383cff75c3ddf https://git.kernel.org/stable/c/cf6c993c0feca7984797e634deba3c80342e199a