CVE-2026-64091

CVE CVE-2026-64091EUVD EUVD-2026-45776Published 2026-07-19T15:40:00.000ZLast changed 2026-08-05T12:39:07.000ZCVSS 9.8

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: batman-adv: tt: fix TOCTOU race for reported vlans The local TT based TVLV is generated by first checking the number of VLANs which have at least one TT entry. A new buffer with the correct size for the VLANs is then allocated. Only then, the list of VLANs s used to fill the VLAN entries in the buffer. During this time, the meshif_vlan_list_lock is held. But the actual number of TT entries of each VLAN can still increase during this time - just not the number of VLANs in the list. But the prefilter used in the buffer size calculation might still cause an increase of the number of VLANs which need to be stored. Simply because a VLAN might now suddenly have at least one entry when it had none in the pre-alloc check - and then needs to occupy space which was not allocated. It is better to overestimate the buffer size at the beginning and then fill the buffer only with the VLANs which are not empty.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux 4.9.217 <4.10; 16116dac23396e73c01eeee97b102e4833a4b205 <724a8eb4155669797c96b70d70e354284ae3b5a8; 4.14.174 <4.15; 16116dac23396e73c01eeee97b102e4833a4b205 <b4d4efd4e351593c81e9293d4b4408d244fa5ee7; patch: 7.1; 3.16.60 <3.17; 16116dac23396e73c01eeee97b102e4833a4b205 <211ea59988e1cba43cb0367ad65d379b56f9c3bd; 3134c5a32810c510f1f447c135cec346acbb71c3; e861e03a1b5b615ad1b57b1802b17e260eedccfe; patch: 7.0.11; 16116dac23396e73c01eeee97b102e4833a4b205 <94d27005016be15ffc638b2ecbc4d58805ad7b48; 16116dac23396e73c01eeee97b102e4833a4b205 <4cc85aec8d3c9ab4dc716dc9f1ed36fca16b227f; 90ae6475b1753f0c1a4c66034b5666de3189fac8; patch: 5.10.259; patch: 6.18.34; patch: 6.12.93; 16116dac23396e73c01eeee97b102e4833a4b205 <e4236bf3ec8d6bb15d0d8d825dcf9933a7d6666b; patch: 5.15.210; 16116dac23396e73c01eeee97b102e4833a4b205 <9a9c859457bc440a55773e01ff18b1bb5bab6836; patch: 6.6.143; patch: 6.1.176; 4.17; 16116dac23396e73c01eeee97b102e4833a4b205 <65a1e67339aa8c95ac544b796946af388930ee23; patch: 0; 0b81edc8818903c64c4d121bc51cd5825be8cc67; 4.4.217 <4.5

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.