CVE-2026-72014

CVE CVE-2026-72014EUVD EUVD-2026-59113Veröffentlicht 2026-08-15T05:51:42.000ZZuletzt geändert 2026-08-17T05:39:26.000ZCVSS 9.8

Was das Advisory beschreibt

In the Linux kernel, the following vulnerability has been resolved: drbd: reject data replies with an out-of-range payload size recv_dless_read() receives a P_DATA_REPLY from a peer into the bio of an outstanding read request. The peer-supplied payload length reaches it as the signed int data_size, and two peer-controlled inputs can make it negative. With a negotiated data-integrity-alg the digest length is subtracted first, so a reply whose payload is smaller than the digest underflows data_size. With no integrity algorithm (the default) data_size is assigned from the unsigned h95/h100 wire length and drbdd() never bounds it for a payload-carrying command, so a length above INT_MAX casts it negative; this path needs no non-default feature. The bio receive loop then computes expect = min_t(int, data_size, bv_len), which is negative, and drbd_recv_all_warn(mapped, expect) receives with a size_t of SIZE_MAX into the first mapped page. The sibling receive path read_in_block() is not affected: it uses an unsigned size and rejects it against DRBD_MAX_BIO_SIZE before receiving. Reject a data reply whose size is negative after the optional digest subtraction, covering both triggers. Impact: a malicious or man-in-the-middle DRBD peer copies attacker-chosen bytes past a bio page in the receiver, corrupting kernel memory. A node that reads from its peer (a diskless node, or read-balancing to the peer) is exposed in the default configuration; data-integrity-alg is not required.

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: 6.6.145; 2.6.33; b411b3637fa71fce9cf2acf0639009500f5892fe <741a682535deffe9ab7e5c89caf83571efbc9dd9; b411b3637fa71fce9cf2acf0639009500f5892fe <f16866c62656865854106b79bcf6e4ca97a51a92; patch: 7.2; patch: 6.1.178; patch: 0; patch: 6.12.97; b411b3637fa71fce9cf2acf0639009500f5892fe <5f59a8142000f0b8f75c432209ead73c424a745d; b411b3637fa71fce9cf2acf0639009500f5892fe <38cc4867540ae8beedfe41a1a1a6ed37052c77d6; patch: 7.1.5; patch: 5.10.261; b411b3637fa71fce9cf2acf0639009500f5892fe <f14e87d7b166490bceb9603b39310e51595d05b9; b411b3637fa71fce9cf2acf0639009500f5892fe <bca33f5442c3094511719d9db792ce3165d87e76; b411b3637fa71fce9cf2acf0639009500f5892fe <bd910a7660d280595ef94cb6d193951d855d330f; b411b3637fa71fce9cf2acf0639009500f5892fe <648d4317326e6aa3f8c05cbf0fd14cc2eba6ca99; patch: 6.18.40; patch: 5.15.212

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.