CVE-2026-80558
CVE CVE-2026-80558EUVD EUVD-2026-66473Published 2026-08-26T14:37:24.000ZLast changed 2026-08-27T05:01:46.000ZCVSS 9.8
What the advisory describes
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 ]
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 5e8d4d36bf23bb7baf027c479d54395840219928 <4f392fec075562dc93bb0c69f37423ca2af9b48f; 5e8d4d36bf23bb7baf027c479d54395840219928 <dfe1877d351b99eb1b1a62a3fc2d174220e88e20; 5e8d4d36bf23bb7baf027c479d54395840219928 <6799d4a916ffcb3d450d8440f9fe0f0862f768d6; patch: 6.1.184; patch: 6.6.153; 5e8d4d36bf23bb7baf027c479d54395840219928 <3660b98d1204b419f6a77e9a295f148dcf38d042; patch: 6.12.105; patch: 6.18.46; patch: 0; patch: 7.1.10; 5e8d4d36bf23bb7baf027c479d54395840219928 <e2ffeec85201b2bb748e99e12539ee1b92f62796; patch: 5.10.266; 5e8d4d36bf23bb7baf027c479d54395840219928 <e009c5f0ad634c62f5c48a41f1f3c019ecf52555; patch: 7.2; 5e8d4d36bf23bb7baf027c479d54395840219928 <505fc50b8ff8e687b7e3ef6866269dea27366224; patch: 5.15.217; 3.15; 5e8d4d36bf23bb7baf027c479d54395840219928 <1c705fe8e59c6b16f48964973fb23c8ec4735b73
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.