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 C471A4457C9 for ; Wed, 26 Aug 2026 14:39:51 +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=1787755195; cv=none; b=ujr3P7Bzk1Jpxyei5ztV6zfxoBfyD7kcfduR+8yzMD8Fvu2QaFINKAmgemuSVIolNMSL/77l9y4R1wFsHNRBS2TVOIdKWIU0Ajx2MAs9pl++Lc2ixFqX3wLEBN5N9/vel4QjLFCXF76rDMm4NsAF/ulOS8ldq5UY7SPoRb6FQ1Y= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787755195; c=relaxed/simple; bh=DkA+Jp6TmBfjPT+DllErEbV6fHUcZFznjwQs28L9ip8=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=TgLyfFuvvkfetXStJ1uKH4VS5WJ5Vc29YFyX7u2KKg3+CkzPXZpJpBDsYz/wRoeshAvGGnnhMhwY8UidXfG/wtTJyE8QwEulhFdPrcP1k6wEpujNZFs+o3tsE7OPiAPnpnZTCcex6ustAlJ09e47KdR+yMgq0cH6DEbYn3MZQaw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=T36yQY5A; 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="T36yQY5A" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0B5431F00A3E; Wed, 26 Aug 2026 14:39:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1787755190; bh=mIqQ9/B2in/gAsta6kVWOe8CShoLTC/wiDrowUFQ4mc=; h=From:To:Cc:Subject:Date:Reply-To; b=T36yQY5AU2RypyGycCzL/nMDYNtT4Q/JRcOIKdKksgXrVLTA4WNZCjwlTaWqu9Wtl X9u7aefmEywwf/tHcfbKeC88IBD2RqFqs6x/CgI1E2e62eQDwT6tLBIHhaAIX6raN/ s/dmF04Qqu3SPx36LIxAM8KykRli76CBH1Kbg+yQ= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-80558: libceph: Avoid using invalid osd indices from primary_temp Date: Wed, 26 Aug 2026 16:37:54 +0200 Message-ID: <2026082609-CVE-2026-80558-e557@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=4140; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=knSubD+00C6USRXUdYGBZPMUENHBuFnq85MV1AdFzn0=; b=owGbwMvMwCRo6H6F97bub03G02pJDFl9v8T+zczOqLkQfFxhz+OugP+5DzLdlbZcCrtkZ9m3c hKrc6hARywLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAEzkoRLDgjP7ez2Za+9Wz5pz +ET4mzMt+yVaqxhmMWet4DQ2P9ge4KnXX5dQ4eQ+nbEeAA== 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: libceph: Avoid using invalid osd indices from primary_temp A corrupted osdmap received from a Ceph monitor or OSD may contain osd indices in its pg_temp, primary_temp, pg_upmap, and pg_upmap_items parts that don't exist, i.e., that are greater than max_osd or smaller than CEPH_HOMELESS_OSD (-1). These indices are used to create the up and acting set in ceph_pg_to_up_acting_osds(), called from calc_target(). While most of these osd indices are checked, the one from primary_temp is not. Subsequently, this may lead to calc_target() returning this (potentially invalid) index as target osd for a (linger) request. Because the osd_state, osd_weight, and osd_addr arrays only contain max_osd entries (with indices 0 to max_osd -1), this leads to out-of-bounds accesses when trying to read values from these arrays. This patch fixes the issue by adding a check to get_temp_osds(), so that only valid osd indices from primary_temp are used, and it falls back to using the primary from pg_temp or the up set if it is invalid. [ idryomov: changelog ] The Linux kernel CVE team has assigned CVE-2026-80558 to this issue. Affected and fixed versions =========================== Issue introduced in 3.15 with commit 5e8d4d36bf23bb7baf027c479d54395840219928 and fixed in 5.10.266 with commit 505fc50b8ff8e687b7e3ef6866269dea27366224 Issue introduced in 3.15 with commit 5e8d4d36bf23bb7baf027c479d54395840219928 and fixed in 5.15.217 with commit 1c705fe8e59c6b16f48964973fb23c8ec4735b73 Issue introduced in 3.15 with commit 5e8d4d36bf23bb7baf027c479d54395840219928 and fixed in 6.1.184 with commit dfe1877d351b99eb1b1a62a3fc2d174220e88e20 Issue introduced in 3.15 with commit 5e8d4d36bf23bb7baf027c479d54395840219928 and fixed in 6.6.153 with commit e2ffeec85201b2bb748e99e12539ee1b92f62796 Issue introduced in 3.15 with commit 5e8d4d36bf23bb7baf027c479d54395840219928 and fixed in 6.12.105 with commit 6799d4a916ffcb3d450d8440f9fe0f0862f768d6 Issue introduced in 3.15 with commit 5e8d4d36bf23bb7baf027c479d54395840219928 and fixed in 6.18.46 with commit 4f392fec075562dc93bb0c69f37423ca2af9b48f Issue introduced in 3.15 with commit 5e8d4d36bf23bb7baf027c479d54395840219928 and fixed in 7.1.10 with commit e009c5f0ad634c62f5c48a41f1f3c019ecf52555 Issue introduced in 3.15 with commit 5e8d4d36bf23bb7baf027c479d54395840219928 and fixed in 7.2 with commit 3660b98d1204b419f6a77e9a295f148dcf38d042 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-80558 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: net/ceph/osdmap.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/505fc50b8ff8e687b7e3ef6866269dea27366224 https://git.kernel.org/stable/c/1c705fe8e59c6b16f48964973fb23c8ec4735b73 https://git.kernel.org/stable/c/dfe1877d351b99eb1b1a62a3fc2d174220e88e20 https://git.kernel.org/stable/c/e2ffeec85201b2bb748e99e12539ee1b92f62796 https://git.kernel.org/stable/c/6799d4a916ffcb3d450d8440f9fe0f0862f768d6 https://git.kernel.org/stable/c/4f392fec075562dc93bb0c69f37423ca2af9b48f https://git.kernel.org/stable/c/e009c5f0ad634c62f5c48a41f1f3c019ecf52555 https://git.kernel.org/stable/c/3660b98d1204b419f6a77e9a295f148dcf38d042