CVE-2026-80558
libceph: Avoid using invalid osd indices from primary_temp
Reported by linux · Published August 26, 2026
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 ]
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel6.12-tools | Amazon Linux | 1:6.12.110-135.201.amzn2023 |
| Linux | Linux | e2ffeec85201b2bb748e99e12539ee1b92f62796, dfe1877d351b99eb1b1a62a3fc2d174220e88e20, 505fc50b8ff8e687b7e3ef6866269dea27366224, 3.15, 1c705fe8e59c6b16f48964973fb23c8ec4735b73 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 5e8d4d36bf23bb7baf027c479d54395840219928, 5e8d4d36bf23bb7baf027c479d54395840219928, 5e8d4d36bf23bb7baf027c479d54395840219928 |
| Linux | Linux | 3.15, 0, 5.10.266 |
| amazon:2023 | kernel6.12-tools | 0 |
| Linux | Linux | 7.2, 7.1.10, 6.18.46 |
| amazon:2023 | kernel6.18-devel | 0 |
| amazon:2023 | perf | 0 |
| amazon:2023 | kernel6.12-devel | 0 |
| amazon:2023 | kernel6.12 | 0 |
| amazon:2023 | kernel | 0 |
| amazon:2023 | kernel6.18-modules-extra | 0 |
| amazon:2023 | kernel-modules-extra-common | 0 |
| amazon:2023 | microvm-kernel6.18 | 0 |
| amazon:2023 | bpftool6.12 | 0 |
| amazon:2023 | kernel6.18-tools | 0 |
| amazon:2023 | bpftool | 0 |
| amazon:2023 | python3-perf6.12 | 0 |
| amazon:2023 | kernel-livepatch-6.12.110-135.201 | 0 |
| amazon:2023 | kernel-headers | 0 |
| amazon:2023 | kernel6.18-modules-extra-common | 0 |
| amazon:2023 | python3-perf | 0 |
…and 18 more
Timeline
- Aug 26, 2026 CVE Published
- Aug 27, 2026 EPSS Score (30 in total, the first dated here)
- Sep 2, 2026 Security Advisory
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-80558
vulnetix vdb fixes CVE-2026-80558
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-80558/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart