CVE-2026-72029

CVE CVE-2026-72029EUVD EUVD-2026-58987Veröffentlicht 2026-08-15T05:51:52.000ZZuletzt geändert 2026-08-17T05:39:34.000ZCVSS 8.8

Was das Advisory beschreibt

In the Linux kernel, the following vulnerability has been resolved: net: wwan: iosm: bound device offsets in the MUX downlink decoder mux_dl_adb_decode() walks a chain of aggregated datagram tables using offsets and lengths taken from the modem. first_table_index, next_table_index, table_length, datagram_index and datagram_length are all device supplied le values. Only first_table_index was checked, and only for being non zero. The decoder then formed adth = block + adth_index and read the table header and the datagram entries with no bound against the received skb. A modem that reports an index or a length past the downlink buffer makes the decoder read out of bounds. The buffer is IPC_MEM_MAX_DL_MUX_LITE_BUF_SIZE and skb->len is at most that, so skb->len is the real limit, but none of these in band offsets were checked against it. The table chain is also followed with no forward progress check. The loop takes the next table from adth->next_table_index and stops only when that reaches zero. A modem can stage two tables that point at each other, so the loop never ends. It runs in softirq and clones the skb on every pass. Validate every device offset and length against skb->len before use. The block header must fit. Each table header, on entry and after every next_table_index, must lie inside the skb. The datagram table must fit. Each datagram index and length must stay inside the skb. The header padding must not exceed the datagram length so the receive length does not wrap. Require each next_table_index to move forward so the chain cannot cycle. This was reproduced under KASAN as a slab out of bounds read on a normal downlink receive once the iosm net device is up.

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.1.178; patch: 6.12.97; 5.18; 1f52d7b622854b8bd7a1be3de095ca2e1f77098e <2b822df8e498aa6ca828e16afd8ffec27f7e4c88; 1f52d7b622854b8bd7a1be3de095ca2e1f77098e <155851e501d6c649cbcfcca6472dc26269b04b6b; patch: 6.18.40; patch: 7.1.5; 1f52d7b622854b8bd7a1be3de095ca2e1f77098e <55cfea8e8d9117ad086d1e1a0ff87f306f8e3ad0; 1f52d7b622854b8bd7a1be3de095ca2e1f77098e <77f0023f22f6a2616ae128e9c93961b24ae52611; patch: 6.6.145; 1f52d7b622854b8bd7a1be3de095ca2e1f77098e <07f5eb6d268a37bd9e131079489655cd599182e0; patch: 7.2; 1f52d7b622854b8bd7a1be3de095ca2e1f77098e <526b8ef54668780c8f69e0211c342763d5dcbad1; patch: 0

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.