CVE-2026-72029

Description

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.

Gravité et risque d'exploitation

CVE-2026-72029 obtient un score CVSS de 8.8/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.40 %, ce qui la place devant 32.4 % des CVE référencées.

Que faire ?

• Vérifiez si Linux (versions <=6.1.*, 7.1.5, 6.18.40, <=6.12.*, 5.18, 0, <=7.1.*, <5.18, <526b8ef54668780c8f69e0211c342763d5dcbad1, 6.1.178, 6.12.97, <=6.6.*, 1f52d7b622854b8bd7a1be3de095ca2e1f77098e, <77f0023f22f6a2616ae128e9c93961b24ae52611, <155851e501d6c649cbcfcca6472dc26269b04b6b, <=6.18.*, 6.6.145, <07f5eb6d268a37bd9e131079489655cd599182e0, <=*, <55cfea8e8d9117ad086d1e1a0ff87f306f8e3ad0, <2b822df8e498aa6ca828e16afd8ffec27f7e4c88, 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

• https://git.kernel.org/stable/c/155851e501d6c649cbcfcca6472dc26269b04b6b
• https://git.kernel.org/stable/c/2b822df8e498aa6ca828e16afd8ffec27f7e4c88
• https://git.kernel.org/stable/c/55cfea8e8d9117ad086d1e1a0ff87f306f8e3ad0
• https://git.kernel.org/stable/c/07f5eb6d268a37bd9e131079489655cd599182e0
• https://git.kernel.org/stable/c/77f0023f22f6a2616ae128e9c93961b24ae52611
• https://git.kernel.org/stable/c/526b8ef54668780c8f69e0211c342763d5dcbad1