CVE-2026-80558

Critical

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 ]

SeverityCritical
CVSS9.8
Exploit probability—
ProductLinux
PublishedAug 26, 2026
First seenAug 26, 2026

How to fix

Update
  • Linux Linux505fc50b8ff8e687b7e3ef6866269dea27366224, 1c705fe8e59c6b16f48964973fb23c8ec4735b73, dfe1877d351b99eb1b1a62a3fc2d174220e88e20, e2ffeec85201b2bb748e99e12539ee1b92f62796, 6799d4a916ffcb3d450d8440f9fe0f0862f768d6, 4f392fec075562dc93bb0c69f37423ca2af9b48f, e009c5f0ad634c62f5c48a41f1f3c019ecf52555, 3660b98d1204b419f6a77e9a295f148dcf38d042 or later

Affected products

ProductAffected versionsFixed in
Linux Linux5e8d4d36bf23bb7baf027c479d54395840219928 ≤ v < 505fc50b8ff8e687b7e3ef6866269dea27366224, 5e8d4d36bf23bb7baf027c479d54395840219928 ≤ v < 1c705fe8e59c6b16f48964973fb23c8ec4735b73, 5e8d4d36bf23bb7baf027c479d54395840219928 ≤ v < dfe1877d351b99eb1b1a62a3fc2d174220e88e20, 5e8d4d36bf23bb7baf027c479d54395840219928 ≤ v < e2ffeec85201b2bb748e99e12539ee1b92f62796, 5e8d4d36bf23bb7baf027c479d54395840219928 ≤ v < 6799d4a916ffcb3d450d8440f9fe0f0862f768d6, 5e8d4d36bf23bb7baf027c479d54395840219928 ≤ v < 4f392fec075562dc93bb0c69f37423ca2af9b48f, 5e8d4d36bf23bb7baf027c479d54395840219928 ≤ v < e009c5f0ad634c62f5c48a41f1f3c019ecf52555, 5e8d4d36bf23bb7baf027c479d54395840219928 ≤ v < 3660b98d1204b419f6a77e9a295f148dcf38d042, 3.15505fc50b8ff8e687b7e3ef6866269dea27366224, 1c705fe8e59c6b16f48964973fb23c8ec4735b73, dfe1877d351b99eb1b1a62a3fc2d174220e88e20, e2ffeec85201b2bb748e99e12539ee1b92f62796, 6799d4a916ffcb3d450d8440f9fe0f0862f768d6, 4f392fec075562dc93bb0c69f37423ca2af9b48f, e009c5f0ad634c62f5c48a41f1f3c019ecf52555, 3660b98d1204b419f6a77e9a295f148dcf38d042

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.