CVE-2026-74598

Description

In the Linux kernel, the following vulnerability has been resolved: ipv6: fix Route Information option length validation rt6_route_rcv() validates the Route Information option (RFC 4191) length against the prefix length, but both checks are off by one. rinfo->length is the ND option length in units of 8 octets and it *includes* the 8-byte option header, so an option carrying N bytes of prefix has length == 1 + N/8. RFC 4191 section 2.3 requires length 3 when Prefix Length is greater than 64, and 2 or 3 when it is greater than 0. The code accepts length >= 2 and length >= 1 respectively. ipv6_addr_prefix() then copies prefix_len/8 bytes out of rinfo->prefix, so a Router Advertisement with (prefix_len=128, length=2) or (prefix_len=64, length=1) makes the kernel read up to 8 bytes past the end of the option. Those bytes end up in the prefix of the route that gets installed, so they are visible to userspace: # RA with a Route Information option (prefix_len=128, length=2) # followed by a source link-layer address option, 01 01 de ad be ef ca fe $ ip -6 route show 2001:db8:dead:beef:101:dead:beef:cafe via fe80::1234 dev veth0 proto ra ^^^^^^^^^^^^^^^^^^ the next option, read out of bounds When the Route Information option is the last one in the packet, those eight bytes come from the skb tail room instead. Reject the option lengths RFC 4191 does not allow.

Gravité et risque d'exploitation

CVE-2026-74598 obtient un score CVSS de 7.5/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.43 %, ce qui la place devant 35.4 % des CVE référencées.

Que faire ?

• Vérifiez si Linux (versions <=6.1.*, 70ceb4f53929f73746be72f73707cd9f8753e2fc, <=6.12.*, 6.6.152, <7309529f257ae18e72112ef9f614edfd6df229bb, 0, <3b2231e358d26e3aec5d8040b1fb777af03c5f05, <=7.1.*, 5.15.216, <=5.10.*, <=6.6.*, 7.1.9, <da64ed1f346ba84df574d6469fa2e422b2511719, 6.1.183, <d1ad8fb2ac6a1afb71dc22d9ae8efb4dda96c824, <=6.18.*, 2.6.17, 6.12.104, 6.18.45, <=*, <=5.15.*, <0b9e02f3bd31c888f2ccdc0ca08e546d6abe9c4d, <2.6.17, 5.10.265, <7eac87396c44a312be457ef41d4c5687883be9a2, 7.2, <2f6f94eda12430fb41b24b44a71e2ea4e93561d7, <ff3cb05289b8a4ef95fa7ea14c7d34818359edbb) 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/2f6f94eda12430fb41b24b44a71e2ea4e93561d7
• https://git.kernel.org/stable/c/7eac87396c44a312be457ef41d4c5687883be9a2
• https://git.kernel.org/stable/c/7309529f257ae18e72112ef9f614edfd6df229bb
• https://git.kernel.org/stable/c/0b9e02f3bd31c888f2ccdc0ca08e546d6abe9c4d
• https://git.kernel.org/stable/c/ff3cb05289b8a4ef95fa7ea14c7d34818359edbb
• https://git.kernel.org/stable/c/3b2231e358d26e3aec5d8040b1fb777af03c5f05
• https://git.kernel.org/stable/c/da64ed1f346ba84df574d6469fa2e422b2511719
• https://git.kernel.org/stable/c/d1ad8fb2ac6a1afb71dc22d9ae8efb4dda96c824