CVE-2026-80557

Vulnérabilité critique dans Linux (Linux)

CVSS 9.8 · Critique
EPSS 0.5%
Linux•Linux•Versions : 6.1.185, <=6.1.*, <=6.12.*, 6.12.106, 0, 5.10.267, <=7.1.*, 6.6.154, <85479b7d65b4ebcb07fbbe57230976793974ab4a, <=5.10.*, <=6.6.*, <c59219a6b62d74936963983e5815524c3de8dd79, a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c, <00ead17c7de137a692edee59f2772e6af687e8eb, <4.9, <=6.18.*, 6.18.47, 7.1.10, <7130d94846dadbb97b6b7f4d78a3a7bba6e3daa1, <=*, 4.9, <=5.15.*, <f161be39201eb5f9b1f58fb8f90b8a9cd3931eb6, <eab3eeb68bfc639d74f27256f05546af5c4f787d, <cb8246e5846dbbe34930903a90c7a90dd8e5910b, 7.2, <1c824e7c75bb4adf19553dd4ea944a5d83096be8, 5.15.218

Description

In the Linux kernel, the following vulnerability has been resolved: libceph: fix OOB read in decode_watchers() via missing bounds check ceph_start_decoding() validates that struct_len bytes remain in the buffer after the encoding header, but accepts struct_len=0 as valid: ceph_decode_need(p, end, 0, bad) always passes. When a malicious or compromised OSD sends an obj_list_watch_response_t reply with struct_len=0, ceph_start_decoding() returns success with p == end, leaving zero bytes guaranteed for subsequent reads. The immediately following ceph_decode_32(p) in decode_watchers() has no preceding bounds check. With p == end this is a 4-byte read past the validated buffer boundary. The garbage value is then passed directly to kzalloc_objs() as the watcher count. The sibling function decode_watcher() already uses the safe variants (ceph_decode_copy_safe, ceph_decode_64_safe, ceph_decode_skip_32) after its own ceph_start_decoding() call. decode_watchers() is the only site that uses the bare variant, confirming an oversight. Fix by replacing ceph_decode_32(p) with ceph_decode_32_safe(p, end, *num_watchers, bad), consistent with the established pattern. Attacker model: a malicious or compromised OSD in a multi-tenant Ceph deployment (e.g. cloud) can trigger this against any kernel client that calls CEPH_OSD_OP_LIST_WATCHERS, without any further privileges beyond OSD session establishment. [ idryomov: trim changelog ]

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions 6.1.185, <=6.1.*, <=6.12.*, 6.12.106, 0, 5.10.267, <=7.1.*, 6.6.154, <85479b7d65b4ebcb07fbbe57230976793974ab4a, <=5.10.*, <=6.6.*, <c59219a6b62d74936963983e5815524c3de8dd79, a4ed38d7a180f184a6e7aedd09db9ca4b1e6a71c, <00ead17c7de137a692edee59f2772e6af687e8eb, <4.9, <=6.18.*, 6.18.47, 7.1.10, <7130d94846dadbb97b6b7f4d78a3a7bba6e3daa1, <=*, 4.9, <=5.15.*, <f161be39201eb5f9b1f58fb8f90b8a9cd3931eb6, <eab3eeb68bfc639d74f27256f05546af5c4f787d, <cb8246e5846dbbe34930903a90c7a90dd8e5910b, 7.2, <1c824e7c75bb4adf19553dd4ea944a5d83096be8, 5.15.218) 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