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=1795154134; b=wgNHOQQYyCS57qpvM9Sx0WvsgWDZL8w/JDubU8PWzrHdBeuisFhOmOWxt8U2S1UhL3SB GWT1qUi8T0IqIVjfDSjRmzOVQ8YuK16pRcKM3wPAlDAggwvEDlJs+/pHKDkmOB/eguUaO rveTbZDXLMjlPLS5gJHYCWtQqiia+fMhJqRHM14Fe+a0A99cThegVEFzkKG0yO5PFLTBr sGxk3UYsasAVPttTLwBQP27/+sFFQu13E9nwiG828x6OMaJrZApoxqgoMS7wQY2grA2fU IXDilQmKkucnpR/jrhzLMrWp9VfxqbbaDCOq9I+aZPTNxUuu1peRRyKjtH6XVBoihOQ== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154134; 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=SpIjT99eH/gIykfjeviMjZlC9zVfuG80WpgOaMg1gkQ=; b=FDn13TP0zxCcrQJC95I45SyspAdjXzX6i7pfsonlI+94ILnQXpASV1dOSWpEmiSIwuih uU2RPdVo+N+DyrvzdehFag4aYxhLP6z6CadIPsdPeoqsBQbXf8lGUg4Zfjvltu+4BklEj VwuAE350XS8WHNkaaWSkPkOSLdWKx7r2JKEvFntNGT/h5BtVB3774XVqVPZHE4RVCSYy6 /zMc2SB8T8Tzj4/+GPfOasTdgDaBfA9zzXuM/bwh8ZjyzuYVQeNzpCZVIxAd75EZJeSaq LxIHNSA+rXtUxdq22LSRyUrDqOibQFeYX1Dcb7A2aQ1cmjPWO60dZSs5dPYegjHMBvQ== 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=gBWjmaNv; 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 02C69606A320 for ; Fri, 20 Nov 2026 05:55:33 +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=gBWjmaNv Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0A6C51F000C4; Fri, 20 Nov 2026 05:55:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154133; bh=SpIjT99eH/gIykfjeviMjZlC9zVfuG80WpgOaMg1gkQ=; h=From:To:Cc:Subject:Date:Reply-To; b=gBWjmaNvl0Duhu7bc+aBpvstpNeobSfRS3IGCgIspXkgtN0fKCg7BMhfmRlR6XOkH pUL61cStz2drtSAng+ijMO4gNUEFMcG8B3/TSBzidM8dKBtyxr3UczdV16TfsxQ4Ng aeisI4mFVnhcmK1zSXdNhHYoV6AhUUaAkhmeccy4= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99601: udf: check the unallocated space table when it is loaded Date: Fri, 20 Nov 2026 06:49:47 +0100 Message-ID: <2026112026-CVE-2026-99601-4a4e@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=4302; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=v6GREtBJh90dnUmywjC3hIQ42D4nUIJ67WvPZyXrHdo=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/76c5in8r1+OaFRt5fJVr6a3186pjEznmXz/TwnOh0 0pWsuNqRywLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAEwkmYthnuKDB+YS2h9OfPqe 01ti89W+gkHrE8OC5f135rSu8vA3Yoo1Y/65WPIWK/stAA== 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: check the unallocated space table when it is loaded udf_table_new_block() hands out the first block of the extent closest to its goal and trusts that the extent covers at least one whole block inside the partition. Nothing checks that. A zero-length extent makes it return the block the extent points at, which need not be free, and the subtraction of one block then underflows the length into the type bits, turning the entry into a bogus continuation. An extent running past the end of the partition makes it return blocks behind the partition. Such tables are not only found on crafted images: until the previous commit, udf_table_new_block() itself left zero-length extents behind in tables written by mkudffs, and then converted them into extents running past the partition. Check every extent once when the table is loaded, and refuse read-write access if one is empty, is not a whole number of blocks, or does not lie inside the partition, in the same way as for other allocation information the kernel cannot use. Check first that the table is an Unallocated Space Entry at all: the walk starts at the offset of the allocation descriptors in one, and for a file entry that offset lies before the inode's in-memory copy of the descriptors. Treat a chain of allocation extent descriptors that leads back to itself the same way: the walk would otherwise return the same extents forever, and the mount would never finish. Let a fatal signal interrupt the walk and fail the mount. Refusing read-write access to an empty extent is deliberate. It shows that an old kernel took the last block but left the entry behind. If consumed again, the entry returns an in-use block and turns into a huge bogus extent. Refusing the table before that happens avoids this second allocation; the filesystem can still be mounted read-only. The check cannot detect every overlap that may already exist in a damaged table. This patch should be backported together with the previous one: that patch stops creating new empty extents, and this one rejects existing ones before they are consumed again. The Linux kernel CVE team has assigned CVE-2026-99601 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 6.12.118 with commit 9f3df19234d2c180b9a99b0d3c2472e8fade5043 Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 6.18.64 with commit 88401035fbfcad7067793455326262ac30633586 Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 7.3.5 with commit 302eb1fa5be5e476a633d8ed0fd56ea5efa57374 Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 7.4-rc2 with commit e614c3e35a6699ed691b4d17e1ec4230e34aa3eb 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-99601 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/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/9f3df19234d2c180b9a99b0d3c2472e8fade5043 https://git.kernel.org/stable/c/88401035fbfcad7067793455326262ac30633586 https://git.kernel.org/stable/c/302eb1fa5be5e476a633d8ed0fd56ea5efa57374 https://git.kernel.org/stable/c/e614c3e35a6699ed691b4d17e1ec4230e34aa3eb