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 664F7347537 for ; Mon, 8 Jun 2026 15:47:20 +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=1780933641; cv=none; b=dCF9H4+19ddEO6z1bzfcVNIMWeosXlJ1OlCuHG7BkFvBTscejPeG8Z+sf1Tju47RuzEF8JHWB8a/t6xhJsLD46xM5kDxXHKQl55WHEKoZSzryIawh38XsPashxy1GN0JdR9+tUw+MJYl1o9NP0KUTqpMmGPgRvcPrIdJ4GTn54o= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780933641; c=relaxed/simple; bh=kzTC3nLpKFYwy1YkruFQE/evaC8KypZyYRVNBst5vd8=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=bK4brQ6DTD01TIunt7jhYwvmoexG542UQ4ZXjQnGMCB+eQ+jnw80JKgrAL3SdIk8BK5u8RXuKoVe7aNUMVvuq2UhFXVXakqS/qareECohD7pFf7o3d7CgANCamZHrk6KEbly6DVNcfS3CuT8g3XctfpR+AJQ6k1PsrpEEcRI0Uo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=C17g3Xv9; 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="C17g3Xv9" Received: by smtp.kernel.org (Postfix) with ESMTPSA id A93501F00893; Mon, 8 Jun 2026 15:47:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1780933640; bh=S8EAW5EBTL/RvKvvZ9Du0zcOVGy+U1Iwh4bTFR8fz2M=; h=From:To:Cc:Subject:Date:Reply-To; b=C17g3Xv9toMEForTl2E27hwM+Ajhr50Tp77MO9yx2tF2LsZf6nfIbl4mSYpTF3os9 4NOZHCk8lytz0wwC4s80RUkIfWm4I73cH56r6Qx3UFhAtk4GOYCyWHha09byckPpPc IZgmnwVEJIVaRCW9+Yzx2pNAVXD0y4GSwAYJgXak= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-46303: isofs: validate Rock Ridge CE continuation extent against volume size Date: Mon, 8 Jun 2026 17:46:10 +0200 Message-ID: <2026060859-CVE-2026-46303-d951@gregkh> X-Mailer: git-send-email 2.54.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=5271; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=dFADfbB3HFCXvgVPTZrSI2IgXWsOxvWxmeDi67KKO8E=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlqj3dklpjOfH2DO6lP7kBJzdX9a5i+pB7msiuMvlbx8 CQXt0BGRywLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAEykophhwfUb36S5tsy4Jdy0 7+rmb8rbMivYihgW7F374+Yr/z/3XvnLzS6ZnsB5ZMfO/wA= 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: isofs: validate Rock Ridge CE continuation extent against volume size rock_continue() reads rs->cont_extent verbatim from the Rock Ridge CE record and passes it to sb_bread() without checking that the block number is within the mounted ISO 9660 volume. commit e595447e177b ("[PATCH] rock.c: handle corrupted directories") added cont_offset and cont_size rejection for the CE continuation but did not validate the extent block number itself. commit f54e18f1b831 ("isofs: Fix infinite looping over CE entries") later capped the CE chain length at RR_MAX_CE_ENTRIES = 32 but again left the block number unchecked. With a crafted ISO mounted via udisks2 (desktop optical auto-mount) or via CAP_SYS_ADMIN mount, rs->cont_extent can therefore point at an out-of-range block or at blocks belonging to an adjacent filesystem on the same block device. sb_bread() on an out-of-range block returns NULL cleanly via the block layer EIO path, so there is no memory-safety violation. For in-range reads of adjacent- filesystem data, the CE buffer is parsed as Rock Ridge records and only the text of SL sub-records reaches userspace through readlink(), which makes the info-leak channel narrow and difficult to exploit; still, rejecting the malformed CE outright matches the rejection shape already present in the same function for cont_offset and cont_size. Add an ISOFS_SB(sb)->s_nzones bounds check to rock_continue() next to the existing offset/size rejection, printing the same corrupted-directory-entry notice. The Linux kernel CVE team has assigned CVE-2026-46303 to this issue. Affected and fixed versions =========================== Issue introduced in 3.19 with commit f54e18f1b831c92f6512d2eedb224cd63d607d3d and fixed in 5.10.258 with commit 8356fb821016797f5677cbeee5ddc0d32a95b4be Issue introduced in 3.19 with commit f54e18f1b831c92f6512d2eedb224cd63d607d3d and fixed in 5.15.209 with commit d582e12378bc1637f337622feef762f53c43fd57 Issue introduced in 3.19 with commit f54e18f1b831c92f6512d2eedb224cd63d607d3d and fixed in 6.1.175 with commit bf1bc673c587f5ef7e9c09b94aea7c5a7847d4d9 Issue introduced in 3.19 with commit f54e18f1b831c92f6512d2eedb224cd63d607d3d and fixed in 6.6.140 with commit c9b37c8b73f6368e4750e5ccb0632c380b43c6e5 Issue introduced in 3.19 with commit f54e18f1b831c92f6512d2eedb224cd63d607d3d and fixed in 6.12.88 with commit 22b36fa081f38ab397c7697f9d539211b51a0cfc Issue introduced in 3.19 with commit f54e18f1b831c92f6512d2eedb224cd63d607d3d and fixed in 6.18.30 with commit e69da8eeab74b4f4505024c38a17bce060fe7df8 Issue introduced in 3.19 with commit f54e18f1b831c92f6512d2eedb224cd63d607d3d and fixed in 7.0.7 with commit ef048470c90bc8c1b8318bb2ce329da9ef64b9fe Issue introduced in 3.19 with commit f54e18f1b831c92f6512d2eedb224cd63d607d3d and fixed in 7.1-rc2 with commit a36d990f591320e9dd379ab30063ebfe91d47e1f Issue introduced in 2.6.32.66 with commit 08313e26e06d4aa9ce1cbba1a8e359e9cab9ad56 Issue introduced in 3.2.67 with commit 212c4d33ca83e2144064fe9c2911607fbed5386f Issue introduced in 3.4.107 with commit 96e44adce250199ec9b2b928be66365779ff1b59 Issue introduced in 3.10.64 with commit 1fe5620fcd6c2f0a4a927ee10c8e53196da392f3 Issue introduced in 3.12.36 with commit fbce0d7dc8965c9fb8d411862040239d4a768c71 Issue introduced in 3.14.28 with commit 8190393a88f2b0321263a54f2a9eb5a2aa43be7e Issue introduced in 3.17.8 with commit 486aa789eadcf44ed87f972b209299c516454693 Issue introduced in 3.18.2 with commit b6d20edb6e7cedb4eedb9e0193d20dd488ebae84 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-46303 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/isofs/rock.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/8356fb821016797f5677cbeee5ddc0d32a95b4be https://git.kernel.org/stable/c/d582e12378bc1637f337622feef762f53c43fd57 https://git.kernel.org/stable/c/bf1bc673c587f5ef7e9c09b94aea7c5a7847d4d9 https://git.kernel.org/stable/c/c9b37c8b73f6368e4750e5ccb0632c380b43c6e5 https://git.kernel.org/stable/c/22b36fa081f38ab397c7697f9d539211b51a0cfc https://git.kernel.org/stable/c/e69da8eeab74b4f4505024c38a17bce060fe7df8 https://git.kernel.org/stable/c/ef048470c90bc8c1b8318bb2ce329da9ef64b9fe https://git.kernel.org/stable/c/a36d990f591320e9dd379ab30063ebfe91d47e1f