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=1795154025; b=y1wToiz4Q7AuOXGLs/6LItU6y4zMo/BuFoszfMjcNuDBiQiIhBPurDy5AZ/aX1ZXeXH0 NSzVTqQXDaubngsp/KaD4xcoZe/+UvYmSWgIVxvmzoeNsKHEKqUcT3P/cVHj8InIrdN9E WSeg0QIR1iy8IGeREjb9ro/QmAsKhULfXl2H5jEwNunh4wzK3LeoxXYUEiJJwc4qC2ugV Vo2/mpZk7mFUCfpC/WLEz0rhKg5d+Va02z9HtCANsZV6P/dWDh8aH4xeu/Iu084oFt5dq HKpSWR68c/nm8hy2YjdNeu5GyPe2CLZEqgMz9StKU8Lmoo7TR0gt/XVL8MRV+RASN0w== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154025; 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=LWdE5xa4EzRsnDtHHVwsfmw9CC/uTK+51dIt49FLftM=; b=ZWh75cSdoGOOQYd+D81TEl6wbu4hAfv27A9b0VTpfs4qiCLZ6cAg7artYBJPzoVS71uy XDiuTd7rlITM79Lv2lKKmmGl8gTZvRB9jWEvvETJucsy8ae4lULPKboBpquxoTlhYt9If cQT0RrZLYarQORqFF34WgKnLJvvW94NZAfNtX2h5kbdbYmbx7OTV3LzvR+o/cy+ybvxZV YSRZQO6Gebfx0YlK26TCtPvygxUgew7Stu+kxQlynBA+e3sV1l0eOXik9W4/hB5sK9ank 00Jef6/JCV6NPjPLsaRGRNbn/8t8bQjtQrwRGGyBLcfIfxq6VKhU22bTPhn5W2L1O9Q== 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=MjI4SLwD; 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 3001E606A320 for ; Fri, 20 Nov 2026 05:53:45 +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=MjI4SLwD Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7162B1F000C4; Fri, 20 Nov 2026 05:53:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154025; bh=LWdE5xa4EzRsnDtHHVwsfmw9CC/uTK+51dIt49FLftM=; h=From:To:Cc:Subject:Date:Reply-To; b=MjI4SLwDwWfegUWl8PN4kglDks0bXa0JCrWRVgk+6OE1+3FxIF0xkesx1ZvN4UJLX lj0iEegBGWumkGKki+gcZsyXycV2tcWhHVU+8IiCvw4RaEaEVZFQYj+HVfKqFg499c h61uEnFUWOXQydkBLsBJ0xAes7od68mIMhHO8VRA= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99574: f2fs: bound the SIT/NAT bitmaps by the checkpoint pack Date: Fri, 20 Nov 2026 06:49:20 +0100 Message-ID: <2026112016-CVE-2026-99574-3e18@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=3140; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=7ZWq9qMnr41h6y4uUv3pL53d2QzwayDt/ybcMwZaHtM=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/78fuNkxO5zSc/7x1uYnxhn0+2xQuWvAv/jnpiGnXj Z1F3xds7YhlYRBkYpAVU2T5so3n6P6KQ4pehranYeawMoEMYeDiFICJdEgwzBWbukksbdqTWQf5 exXW8P7v7fz/Lothwfyt198dZvE9z166tG/XrUze598vXQYA 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: f2fs: bound the SIT/NAT bitmaps by the checkpoint pack sit_ver_bitmap_bytesize and nat_ver_bitmap_bytesize are used as memcpy lengths into and out of sbi->ckpt, which is sized from cp_payload alone, and nothing compares either length against that allocation. sanity_check_ckpt() has checked these two fields since c77ec61ca0a4, which added them after a crafted image overran build_sit_info(). That check ties each length to a segment count; it never compares either against the allocation, which is the half this adds. Mounting over-reads in build_sit_info() and build_node_manager(), and the first checkpoint writes the same lengths back through the same pointers, so the over-read's contents reach the on-disk checkpoint. An unmount is enough; the filesystem does not have to be used. Bound both ends the way __bitmap_ptr() lays them out. The three branches differ, so a single sum of the two lengths would still admit a small overflow when cp_payload is non-zero. The Linux kernel CVE team has assigned CVE-2026-99574 to this issue. Affected and fixed versions =========================== Issue introduced in 3.8 with commit 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 and fixed in 6.12.118 with commit ddb9848fd6b2f4e9ed5ef78b20c9720c65a29df5 Issue introduced in 3.8 with commit 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 and fixed in 6.18.64 with commit 9b08fc2d092171af388f83030d54488b87453155 Issue introduced in 3.8 with commit 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 and fixed in 7.3.5 with commit 7f88cd38394a16c326073c8813e7f1f1445bf3ba Issue introduced in 3.8 with commit 39a53e0ce0df01b3cf4bb898c7ae2fd2189647d5 and fixed in 7.4-rc1 with commit 080833a32fd5dc10b3acf2fa9af9b3213e6cb617 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-99574 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/f2fs/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/ddb9848fd6b2f4e9ed5ef78b20c9720c65a29df5 https://git.kernel.org/stable/c/9b08fc2d092171af388f83030d54488b87453155 https://git.kernel.org/stable/c/7f88cd38394a16c326073c8813e7f1f1445bf3ba https://git.kernel.org/stable/c/080833a32fd5dc10b3acf2fa9af9b3213e6cb617