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=1794823232; b=q+Wz94gZCqIMZIQ21kNiJGVG3yijFR5GOkqj6rk8xb3qEd0MTh1/IoCgfMIAg0Zz+E3I GdhC5hxT4yKdTIJHvHJV23U29jl2P79m1CZR3qaRYiwYlUubUjNpbUxshKZ7w+ut8kmlj 1SoS/vLz0TDkVnoCtLqN6BRRk9ySyzCecPLqTsGIMEfI8DdnO67YUIejbepk8dWax0ls6 Z9hth+rHmwd2f5eYX26x2V9mae6HPH10kwgP4cEdgzJFcg5gDqNISbzJid+IoEcoRTtfB CAVm8gHzkHR1ElMf/FCkPLvKFpf5yIQweRuklm0oihngKNUZ5LwQAAjrgKBuA85pvnA== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1794823232; 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=Vvdcqsz/1zpy86ylt+pZu/pJxkiGjosTLQgwQCNxB4s=; b=I6J5bB0I5qjTrPl2adndzNAyqwKTusYbHV2MrLdQaYouTErPqk+Dq82L42QrJbO1QLKN tDFqS7ZVgoGbXVjZZdQS8VY9kiZvva689L4pFtZOGz22lAJ6pN2+JY5URaN341LTR1k1f vsYJfLpjnPo0Tk6rmp6iScA9akm/DPUGZE1t+58zREdBppFiX6zozzzN5fpP7RoydOIv9 qNhx7oudk1f+f39w9Mq2cQ6eWmWkRKZwSBcCRlloGZ3R4bDIyRxqaJ+5wns4ZRt4SSsAL Cck41yy+MYzIvgYHlMYLCUvOzHq8IvYJVQy4ZBF1vCdVZ3McIWKGgfYvfCrq+UzPoAA== 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=wpwtd3Vk; 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 97E4D606A329 for ; Mon, 16 Nov 2026 10:00:32 +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=wpwtd3Vk Received: by smtp.kernel.org (Postfix) with ESMTPSA id 868CD1F000C4; Mon, 16 Nov 2026 10:00:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1794823232; bh=Vvdcqsz/1zpy86ylt+pZu/pJxkiGjosTLQgwQCNxB4s=; h=From:To:Cc:Subject:Date:Reply-To; b=wpwtd3Vkl1zMPfTDu+FAR7W5Bit2akNPcimhvgUNH6n+AmvuPYfqUgqHsMyPu+8g5 dOylwrWiSDUqgXtZ6isdps1bj8mPkolrOEKY6DqOex0SyUA3X7ajOD0ri7OPgWGoKY zEZjCk/vcBXHJPaew9ronlSXQJEHfl8nhgb21dLI= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99311: udf: fix return value for non-recorded-allocated extents in udf_map_block() Date: Mon, 16 Nov 2026 11:00:00 +0100 Message-ID: <2026111642-CVE-2026-99311-e887@gregkh> X-Mailer: git-send-email 2.56.0 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=3216; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=QI7n1WN9MwZ7+ECvN2ESZBdNe0jktnsDUyVX5/UlEc8=; b=owGbwMvMwCRo6H6F97bub03G02pJDFm/rvAdqj34utBraobQwp4nu867FLwVchM37zpff+xWz fTJNYtmd8SyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBEzkUzzI9i1p+VMXlCwN3D X6M88g1k3x6f38Aw30O8uddBdm1HVlZ3/pzXZpsq8rRXAAA= 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: udf: fix return value for non-recorded-allocated extents in udf_map_block() When someone creates a corrupted UDF filesystem where symlink contains other extent type than EXT_RECORDED_ALLOCATED, it can leads to a crash like: Oops: general protection fault KASAN: maybe wild-memory-access RIP: 0010:page_get_link (fs/namei.c:6503) Call Trace: vfs_readlink (fs/namei.c:6419) do_readlinkat (fs/stat.c:583) __x64_sys_readlink (fs/stat.c:605 fs/stat.c:602 fs/stat.c:602) This is because in this case udf_map_block() fails to convert return value of inode_bmap() from 1 to 0. Returned '1' propagates through udf_bread() all the way up to __page_get_link() where it ends up being treated as a folio pointer with obvious results. Move the reset to 0 line outside the if, so udf_map_block() returns either 0 or -errno, even if the extent type is not EXT_RECORDED_ALLOCATED. The Linux kernel CVE team has assigned CVE-2026-99311 to this issue. Affected and fixed versions =========================== Issue introduced in 6.12 with commit c226964ec786f3797ed389a16392ce4357697d24 and fixed in 6.12.117 with commit 0d7f6c2b3c07fa239ebc169280eba9932cc56f46 Issue introduced in 6.12 with commit c226964ec786f3797ed389a16392ce4357697d24 and fixed in 6.18.61 with commit df713b82b4b9671c16b52b60f3412c677719e2b8 Issue introduced in 6.12 with commit c226964ec786f3797ed389a16392ce4357697d24 and fixed in 7.3.2 with commit f022984a4a1c18aa9c506790eb47da000dce95a7 Issue introduced in 6.12 with commit c226964ec786f3797ed389a16392ce4357697d24 and fixed in 7.4-rc1 with commit 0f242ca0878896df30292f4922700a32e8fdd039 Issue introduced in 6.6.59 with commit 493447dd8336607fce426f7879e581095f6c606e Issue introduced in 6.11.6 with commit b22d9a5698abf04341f8fbc30141e0673863c3a6 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-99311 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/udf/inode.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/0d7f6c2b3c07fa239ebc169280eba9932cc56f46 https://git.kernel.org/stable/c/df713b82b4b9671c16b52b60f3412c677719e2b8 https://git.kernel.org/stable/c/f022984a4a1c18aa9c506790eb47da000dce95a7 https://git.kernel.org/stable/c/0f242ca0878896df30292f4922700a32e8fdd039