CVE-2026-80561

CVE CVE-2026-80561EUVD EUVD-2026-66476Veröffentlicht 2026-08-26T14:37:26.000ZZuletzt geändert 2026-08-27T05:01:49.000ZCVSS 9.8

Was das Advisory beschreibt

In the Linux kernel, the following vulnerability has been resolved: libceph: fix multiple unsafe decodes in decode_locker() decode_locker() in cls_lock_client.c contains three unsafe decode operations that allow a malicious or compromised OSD to trigger slab-out-of-bounds reads: 1. ceph_decode_copy() at the locker_id_t name field has no preceding bounds check. With p == end after ceph_start_decoding() accepts struct_len=0, this reads sizeof(ceph_entity_name) = 9 bytes past the validated buffer boundary. 2. *p += sizeof(struct ceph_timespec) after the locker_info_t header is an unchecked pointer advance. A malicious OSD can position p past end, causing all subsequent _safe checks to pass against a bogus boundary. 3. len = ceph_decode_32(p) has no preceding bounds check, and the immediately following *p += len is uncapped. A malicious OSD can send len=0xffffffff, advancing p gigabytes past end and escaping the decode window entirely. Fix all three by replacing bare operations with their safe variants: ceph_decode_copy -> ceph_decode_copy_safe *p += sizeof(...) -> ceph_decode_skip_n ceph_decode_32(p) -> ceph_decode_32_safe *p += len -> ceph_decode_skip_n A new label is added to return -EINVAL on any bounds violation. -EINVAL is appropriate here: the data received from the OSD is structurally malformed, which is an invalid argument to the decode contract regardless of whether the caller or the wire is at fault. Attacker model: a malicious or compromised OSD in a multi-tenant Ceph deployment can trigger this against any kernel client that issues the lock.get_info class method (e.g. during RBD exclusive lock acquisition) without any further privileges beyond OSD session establishment. [ idryomov: use ceph_decode_skip_string() to skip description, trim changelog ]

Quelle: EUVD (ENISA), im Wortlaut der Meldung.

Produkte, die das Advisory nennt

Diese Angaben stammen aus der Meldung selbst, nicht aus einer Prüfung durch uns.

• Linux — Linux patch: 7.2; d4ed4a530562881cc5225050e42d96034f405aae <d1bba38574d095f191557d397d9633f08cd966b1; 4.9; d4ed4a530562881cc5225050e42d96034f405aae <3c3716dc06a34e4ca7f743f5fcfa07fbc5a11070; patch: 0; d4ed4a530562881cc5225050e42d96034f405aae <437b6551cfcc235eea1d735a874f9d421f555e17; patch: 6.18.46; patch: 6.6.153; patch: 6.12.105; d4ed4a530562881cc5225050e42d96034f405aae <1ed45c8d96498725eb54f740172f9068d8673906; patch: 6.1.184; patch: 5.15.217; d4ed4a530562881cc5225050e42d96034f405aae <dbfd83f722a78446ec18a476ef7a38e52240b50a; d4ed4a530562881cc5225050e42d96034f405aae <6265103e78f0ee7e2518de9cf938b94bee9700a0; patch: 5.10.266; d4ed4a530562881cc5225050e42d96034f405aae <fa4aa86fff0c56799c2e3f51a88879053285f4a9; d4ed4a530562881cc5225050e42d96034f405aae <51c8d238fe7236de627ab1a1433694552a904136; patch: 7.1.10

Die genannten Versionen sind die Angabe der Meldung. Patchlage vergleicht keine Versionsnummern und leitet aus ihnen keine Aussage ab — welche Version installiert ist, muss ein Mensch nachsehen.

Im Produktkatalog geführt

Für diese Produkte kann ein Bestand in Patchlage erfasst werden. Ein Advisory dazu erscheint am Morgen danach im Lagebericht.

• Linux — Linux

Patchlage meldet Treffer und Verdachtsfälle. Zu allem anderen sagt dieses System nichts — weder diese Seite noch der Lagebericht behauptet je, dass ein Bestand sicher ist.