Heimdall Security Logo

CVE-2026-68131

Vulnérabilité élevée dans Linux (Linux)

CVSS 7.5 · Élevée
EPSS 0.5%
Linux•Linux•Versions : <cf1167292f606deaddac35ec384eba48f08a68d2, <=6.1.*, <da926959bf791441ba06a80571708c3d0d3cc08f, <=6.12.*, <14995c4250f04b58bf6fc00e0e973a2e1b3cfb9b, <a6c4250b81bd30beae94e1b7a4b26fa1193ad2e4, 6.12.101, 0, <=7.1.*, <2419aa74081007dc4d14ff5640659052dfdfd69a, 5.15.216, <6f33d9d539fb94e5a17589c2dfe271ff9bb64904, <=5.10.*, <=6.6.*, 6.18.42, 7.1.6, 6.1.183, 5.3, <=6.18.*, <5.3, <34f2a2f32af570dfcc532ad70c080629ee1c32b0, <=*, 22e8bd51bb0469d1a524130a057f894ff632376a, <=5.15.*, <b1a61366933224b3ad80975c4d01ac2cc6931ecf, 5.10.265, 6.6.148, 7.2

Description

In the Linux kernel, the following vulnerability has been resolved: rbd: Reset positive result codes to zero in object map update path In a reply message to an RBD request, a positive result code indicates a data payload, which is not allowed for writes. While rbd_osd_req_callback() already resets a positive result code for writes to zero, rbd_object_map_callback() does not. This allows a corrupted reply to an object map update to trigger the rbd_assert(*result < 0) in __rbd_obj_handle_request(). This happens, because rbd_object_map_callback() calls rbd_obj_handle_request() -> __rbd_obj_handle_request() and passes this positive result code. From __rbd_obj_handle_request(), rbd_obj_advance_write() is called, which leaves the positive result code unchanged and returns true. Therefore, the if(done && *result) branch is executed in __rbd_obj_handle_request() and the assertion triggers. This patch fixes the issue by adjusting the logic in the rbd_object_map_callback() path. A positive result code for an object map update is now reset to zero (similar to rbd_osd_req_callback()), and the message is subsequently handled the same way as if the result code was zero from the beginning. Additionally, a WARN_ON_ONCE() is added for this case.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <cf1167292f606deaddac35ec384eba48f08a68d2, <=6.1.*, <da926959bf791441ba06a80571708c3d0d3cc08f, <=6.12.*, <14995c4250f04b58bf6fc00e0e973a2e1b3cfb9b, <a6c4250b81bd30beae94e1b7a4b26fa1193ad2e4, 6.12.101, 0, <=7.1.*, <2419aa74081007dc4d14ff5640659052dfdfd69a, 5.15.216, <6f33d9d539fb94e5a17589c2dfe271ff9bb64904, <=5.10.*, <=6.6.*, 6.18.42, 7.1.6, 6.1.183, 5.3, <=6.18.*, <5.3, <34f2a2f32af570dfcc532ad70c080629ee1c32b0, <=*, 22e8bd51bb0469d1a524130a057f894ff632376a, <=5.15.*, <b1a61366933224b3ad80975c4d01ac2cc6931ecf, 5.10.265, 6.6.148, 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