Heimdall Security Logo

CVE-2026-52955

Vulnérabilité critique dans Linux (Linux)

CVSS 9.8 · Critique
EPSS 0.4%
Linux•Linux•Versions : <=6.1.*, <=7.0.*, <=6.12.*, 0, <ebe76d58a48a48031b98543d86c4cd30a825b622, <cceb10023e76bc89f3fe9238ebd0ccab0fc7c7c5, <2.6.34, 6.18.33, <6e70ef53e818c53eab28d7b0026b7fd03dddaba5, 5.15.209, <ea0d42137f0c06da71e37ffc647aab4c5309599a, 6.12.91, <=5.10.*, <=6.6.*, 6.1.175, 2.6.34, 6.6.141, <4c79fc2d598694bda845b46229c9d48b65042970, 7.1, <=6.18.*, 7.0.10, 5.10.258, <fb176a99e4c1a5a8448a83d83d3606203ba81faa, <3f42508191e129ee6b5ea96578d5cab14f2a013a, <=*, <=5.15.*, <0f3604cbe4df14c5e58288ac9f57511e726a222d, f24e9980eb860d8600cbe5ef3d2fd9295320d229

Description

In the Linux kernel, the following vulnerability has been resolved: libceph: Fix potential out-of-bounds access in crush_decode() A message of type CEPH_MSG_OSD_MAP containing a crush map with at least one bucket has two fields holding the bucket algorithm. If the values in these two fields differ, an out-of-bounds access can occur. This is the case because the first algorithm field (alg) is used to allocate the correct amount of memory for a bucket of this type, while the second algorithm field inside the bucket (b->alg) is used in the subsequent processing. This patch fixes the issue by adding a check that compares alg and b->alg and aborts the processing in case they differ. Furthermore, b->alg is set to 0 in this case, because the destruction of the crush map also uses this field to determine the bucket type, which can again result in an out-of-bounds access when trying to free the memory pointed to by the fields of the bucket. To correctly free the memory allocated for the bucket in such a case, the corresponding call to kfree is moved from the algorithm-specific crush_destroy_bucket functions to the generic crush_destroy_bucket().

Gravité et risque d'exploitation

CVE-2026-52955 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.38 %, ce qui la place devant 30.5 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=7.0.*, <=6.12.*, 0, <ebe76d58a48a48031b98543d86c4cd30a825b622, <cceb10023e76bc89f3fe9238ebd0ccab0fc7c7c5, <2.6.34, 6.18.33, <6e70ef53e818c53eab28d7b0026b7fd03dddaba5, 5.15.209, <ea0d42137f0c06da71e37ffc647aab4c5309599a, 6.12.91, <=5.10.*, <=6.6.*, 6.1.175, 2.6.34, 6.6.141, <4c79fc2d598694bda845b46229c9d48b65042970, 7.1, <=6.18.*, 7.0.10, 5.10.258, <fb176a99e4c1a5a8448a83d83d3606203ba81faa, <3f42508191e129ee6b5ea96578d5cab14f2a013a, <=*, <=5.15.*, <0f3604cbe4df14c5e58288ac9f57511e726a222d, f24e9980eb860d8600cbe5ef3d2fd9295320d229) 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