Heimdall Security Logo

CVE-2026-80558

Vulnérabilité critique dans Linux (Linux)

CVSS 9.8 · Critique
EPSS 0.5%
Linux•Linux•Versions : <505fc50b8ff8e687b7e3ef6866269dea27366224, <=6.1.*, <=6.12.*, <3.15, 5.15.217, 0, <=7.1.*, <3660b98d1204b419f6a77e9a295f148dcf38d042, <=5.10.*, <=6.6.*, <6799d4a916ffcb3d450d8440f9fe0f0862f768d6, 5.10.266, <e2ffeec85201b2bb748e99e12539ee1b92f62796, 3.15, <1c705fe8e59c6b16f48964973fb23c8ec4735b73, <=6.18.*, 5e8d4d36bf23bb7baf027c479d54395840219928, 6.1.184, 7.1.10, <4f392fec075562dc93bb0c69f37423ca2af9b48f, <e009c5f0ad634c62f5c48a41f1f3c019ecf52555, <=*, <dfe1877d351b99eb1b1a62a3fc2d174220e88e20, <=5.15.*, 6.6.153, 6.12.105, 6.18.46, 7.2

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 ]

Gravité et risque d'exploitation

CVE-2026-80558 obtient un score CVSS de 9.8/10, soit une gravité critique. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.51 %, ce qui la place devant 42.5 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <505fc50b8ff8e687b7e3ef6866269dea27366224, <=6.1.*, <=6.12.*, <3.15, 5.15.217, 0, <=7.1.*, <3660b98d1204b419f6a77e9a295f148dcf38d042, <=5.10.*, <=6.6.*, <6799d4a916ffcb3d450d8440f9fe0f0862f768d6, 5.10.266, <e2ffeec85201b2bb748e99e12539ee1b92f62796, 3.15, <1c705fe8e59c6b16f48964973fb23c8ec4735b73, <=6.18.*, 5e8d4d36bf23bb7baf027c479d54395840219928, 6.1.184, 7.1.10, <4f392fec075562dc93bb0c69f37423ca2af9b48f, <e009c5f0ad634c62f5c48a41f1f3c019ecf52555, <=*, <dfe1877d351b99eb1b1a62a3fc2d174220e88e20, <=5.15.*, 6.6.153, 6.12.105, 6.18.46, 7.2) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE