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 BA5DB5678C6 for ; Fri, 11 Sep 2026 19:48:32 +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=1789156132; cv=none; b=k2FD4detGeQQittsbmHwIWzPIc+gWiNhYTiGUASvGFnai72RFNLCQeOuLiJoUKGP6mKY1rTV2PbOcUXxtZbrR4TJiTOJqpUP92OS7ljO1meyTb8+sSKojTyz7rS9C1Fe03wqIoBAiT4WodGX9vfqoavwwmqKxMtmXd21vKf9/s4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789156132; c=relaxed/simple; bh=r7uOi8mUTtnMFQmIM9sxEjcGWB1b2m0DN+8vT0N41ec=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=TxntVdZzGtWdb0OsLUuOPSX5+BCLXN1ZE7eCVHq91DpgQfsKSAjbT9ytJpnK2q/rW/dLoGqvSrA+iOh1JJDxWWsnTb/t3P3zvKlO2e8I5EggJ1ezRi2TWVcegaZbKMUbVSLOTnmZORw0r8LEMlyJgMrEAXoeQaibcR1P2doYLpk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=oK31+YZ5; 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="oK31+YZ5" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5216C1F00898; Fri, 11 Sep 2026 19:48:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789156111; bh=PpMqLaAss5yrM3eSDJLbaj81XbRBjUvEich38gnr0YQ=; h=From:To:Cc:Subject:Date:Reply-To; b=oK31+YZ5KtyoeAyuVG5dd6aG9YQqbZjmzo5MQq3qeXwbHX/UCvxOYyo7EruTNqxoC QUkSbnANZbAAJB1+NRImur7Ai7oAozn1cekU1/aXcnxV2jxJgIjQnptd5PIfE0QYSl itiog+dA4yQ1pbX1WB6mLSbYNsU4e1X0xCkYB7Kg= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-80962: dm-pcache: validate geometry fields from on-disk cache_info Date: Fri, 11 Sep 2026 21:41:08 +0200 Message-ID: <2026091142-CVE-2026-80962-2a9f@gregkh> X-Mailer: git-send-email 2.55.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=2772; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=ukiIfs3JrKzPIjBFxJfqubK3VLHP633Z1brDUsz3XOI=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlLIq1uXtr33UNZriDD8W/Y06WzXQXnHTzvs379ncr2W IkA9acrOmJZGASZGGTFFFm+bOM5ur/ikKKXoe1pmDmsTCBDGLg4BWAibHMYFlx551OpHbBCbu+x 6QY39tbr+E74NpNhwR4tnzOGSSmOC/7O/1lrf65uk39vBQA= 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: dm-pcache: validate geometry fields from on-disk cache_info cache_segs_init() iterates cache_info->n_segs times indexing cache->segments[], which is sized to the cache device geometry, and get_seg_id() takes each segment id from the on-media cache_info and the per-segment next_seg link. Both come from cache device metadata that is only CRC-protected with a fixed public seed, so whoever supplies the cache device on a table load (CAP_SYS_ADMIN) controls them: an oversized n_segs or an out-of-range id drives an out-of-bounds access of cache->segments[] and a wild CACHE_DEV_SEGMENT() pointer into the device mapping -- an out-of-bounds read and write from on-disk data. Reject an n_segs that exceeds the device segment count and a segment id that is out of range before either is used. Valid metadata is unaffected. The Linux kernel CVE team has assigned CVE-2026-80962 to this issue. Affected and fixed versions =========================== Issue introduced in 6.18 with commit 1d57628ff95b32d5cfa8d8f50e07690c161e9cf0 and fixed in 6.18.50 with commit ab5dcde6fa96bc115b85f3621c60e39c66229a90 Issue introduced in 6.18 with commit 1d57628ff95b32d5cfa8d8f50e07690c161e9cf0 and fixed in 7.2.4 with commit 3e19172089ec81132a8a48e802b1034a744209f4 Issue introduced in 6.18 with commit 1d57628ff95b32d5cfa8d8f50e07690c161e9cf0 and fixed in 7.3-rc1 with commit 32d1809da31094ef76fd98dc1f1a8b55ca1295dd 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-80962 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: drivers/md/dm-pcache/cache.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/ab5dcde6fa96bc115b85f3621c60e39c66229a90 https://git.kernel.org/stable/c/3e19172089ec81132a8a48e802b1034a744209f4 https://git.kernel.org/stable/c/32d1809da31094ef76fd98dc1f1a8b55ca1295dd