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=1795099798; b=0yLB3wWu1bJBRdniyhClfsSgYmW8AXUVmBiiXVTPuwkfSsHmhwzVKxR7GhDBrRuS5qNx Otart2M6jdPKmVwXzSUcAEDwSIxQ/PXftHeZcR3gLMnvcQ5I4/pHIQFilPx0BLTzZw5wB xVpv/nmCrc/A+QTatlO1QkQeDBL0JagOaizBaIl6oWvUXu93QVhh7vD4ah/uS2Xfk605e 7Kq/8Hf8WsKftYjdB/lPjvBVSa8/rb2QfLkCe+LbXWyKKd7YVsu/EA3Mejfqbjd1SM5By 91/g1n5qoqpb9UfR85s8tIBrtqm5T10xFNtinR/K1d8Ld8agmFh32ASv8bvjzGHQcsA== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795099798; 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=RwCFXgMj353i5xk04tEW733MXBWU+etBU9USFf4+WMM=; b=PLdocjXcLPGb4LInVfzMxanGEhAZ1JYbxe9TRxKdLgcR3YBdwicX9NRCowFQ2vXkSOJR 1CsyvDeOhfk5O/PZouqYMEor0vwYu+Qq+RZXqfrgZmQ8Pe5Xa5MvkQPN3ZB15BRY9J55f fGWcnaFYJw9Ck4b3Bb8tm1hFFpLZB+6lPUJAJzaLeOr0QEUrbveCLiaeKNLd0BDWeU8mK Kr5C8Ko2h0md4oNVufm693tkmxZPlUgE2YFmoo5/B8hrRglpfLHT1Y/l4RO+j1E+l+Nzm 3h6Q2RFTejVun6yT6ABjYj2jJqOOuG8PeKF1Ff8Mz5dBXx2Uk9eJm4c9Rf5ITHbfo1w== 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="q/JG5eSM"; 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 DE82F606A33D for ; Thu, 19 Nov 2026 14:49:58 +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=q/JG5eSM Received: by smtp.kernel.org (Postfix) with ESMTPSA id 11CBE1F000C5; Thu, 19 Nov 2026 14:49:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795099798; bh=RwCFXgMj353i5xk04tEW733MXBWU+etBU9USFf4+WMM=; h=From:To:Cc:Subject:Date:Reply-To; b=q/JG5eSMGnk6plAnJ/0aNTSx3SVm5/blLnAmb+4Vnb0WjRurm435Oq0skGz3rjbOc CzzsQeiBW8jgp6u2+KFYUINoe1MTJt8CzkVIHP86nUUiB9tuflAXYsyfVh0cC6muEb DRm27vHl2o84Op7EI3yxef+SzxLLP7uK8cMRKN6U= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99430: ocfs2: fix chunk number of the first chunk in a local quota file Date: Thu, 19 Nov 2026 15:25:28 +0100 Message-ID: <2026111902-CVE-2026-99430-8a67@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=5879; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=Lbye9JStYfOdXlj4c2L4DaWv2Y+F/TxsE0n2yGikUiI=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/2Zrn/SyJjJT1Y9NUVXj2cNW2pekOB2fohLxW/Nbw7 fTUi++WdcSyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBENJ4xzM8y/PZ+0WL1X806 F2Z+mr7x23S7FaYMc/isFhnu+3DFdcdMBskXuR0LpAVeLQEA 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: ocfs2: fix chunk number of the first chunk in a local quota file Mounting a crafted OCFS2 image can corrupt kernel memory. When the local quota file header of such an image claims zero chunks, the first quota entry allocated during the mount gets a chunk number taken from a kernel pointer, and releasing that entry clears a bit far outside the chunk bitmap. The write will corrupt the data stored at that address, and the corruption may lead to a system crash or damage unrelated data. Mounting requires CAP_SYS_ADMIN, so it takes an untrusted image, such as removable media or a loop mount of a file from elsewhere. Since the chunk number comes from a kernel pointer, the address of the bit that gets cleared differs from boot to boot, and the issue has been reported under several titles: - BUG: unable to handle kernel paging request in ocfs2_local_release_dquot - KASAN: use-after-free Write in ocfs2_local_release_dquot - KASAN: slab-out-of-bounds Write in ocfs2_local_release_dquot - KASAN: slab-use-after-free Write in ocfs2_local_release_dquot - KFENCE: use-after-free write in ocfs2_local_release_dquot Note that none of these is a use-after-free in the quota code: the chunk and its buffer head are alive. The bit that gets cleared lies far outside the bitmap. KASAN and KFENCE name each report based on the object occupying that address, which explains why the same issue is reported under so many different titles. In the report I sent, the address fell in a free page, which KASAN labels use-after-free. There are known reproducers. Both a syzkaller and a C reproducer are available from the Google Drive link [1] in my report thread. The issue was found by our modified syzkaller, not a theoretical thing found by an LLM. I have not seen it outside fuzzing, so it is not affecting me in the real world. The local quota file in OCFS2 is divided into chunks, and each chunk begins with a header block holding a bitmap of the quota entries that chunk has handed out. Chunks are numbered from zero, and that number is used to convert the file offset of an entry back into a bit position in the bitmap. ocfs2_local_quota_add_chunk() appends a new chunk to the in-memory list and numbers it one past the chunk that was last: list_add_tail(&chunk->qc_chunk, &oinfo->dqi_chunk); chunk->qc_num = list_entry(chunk->qc_chunk.prev, struct ocfs2_quota_chunk, qc_chunk)->qc_num + 1; The predecessor is looked up after the new chunk is added to the list, so if the list was empty, the prev pointer is the list head itself. The head is the dqi_chunk member of struct ocfs2_mem_dqinfo and is not a chunk, so reading qc_num through it lands 16 bytes past the start of the head, on the dqi_gqinode pointer that follows it. The first chunk of the file is then numbered with the lower half of a kernel pointer instead of 0. The list is empty when the local quota file header claims the file has no chunks. ocfs2_local_read_info() takes dqi_chunks from that header without validating it, so an image with dqi_chunks == 0 takes this path when the first quota entry is allocated. ocfs2_create_local_dquot() turns the bad number into a file offset with ol_dqblk_off(), which shifts a 32-bit block number left by the block size bits, so the top bits of such a large block number are lost. ocfs2_local_release_dquot() turns the offset back into a bit index with ol_dqblk_chunk_off(), using the full chunk number, so the lost bits push that index far outside the bitmap, and clearing it corrupts unrelated memory. Compute the chunk number before putting the chunk on the list, and use 0 when the list is empty. The Linux kernel CVE team has assigned CVE-2026-99430 to this issue. Affected and fixed versions =========================== Issue introduced in 2.6.29 with commit 9e33d69f553aaf11377307e8d6f82deb3385e351 and fixed in 6.12.117 with commit 76986d0ad2e1b71a304db59980f7d3440709cf69 Issue introduced in 2.6.29 with commit 9e33d69f553aaf11377307e8d6f82deb3385e351 and fixed in 6.18.61 with commit 59d336153d40649afe86ff57d3bde1ac1588e850 Issue introduced in 2.6.29 with commit 9e33d69f553aaf11377307e8d6f82deb3385e351 and fixed in 7.3.2 with commit 5778be09eab716b7d37f653d72c2c34a25f6ba05 Issue introduced in 2.6.29 with commit 9e33d69f553aaf11377307e8d6f82deb3385e351 and fixed in 7.4-rc1 with commit 4effccfd50baee4f325694964aeee997dca7bd96 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-99430 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/ocfs2/quota_local.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/76986d0ad2e1b71a304db59980f7d3440709cf69 https://git.kernel.org/stable/c/59d336153d40649afe86ff57d3bde1ac1588e850 https://git.kernel.org/stable/c/5778be09eab716b7d37f653d72c2c34a25f6ba05 https://git.kernel.org/stable/c/4effccfd50baee4f325694964aeee997dca7bd96