CVE-2026-72226
Linux kernel vulnerability
- Published15 Aug 2026
Description
In the Linux kernel, the following vulnerability has been resolved: batman-adv: tt: prevent TVLV OOB check overflow A TT unicast TVLV contains the number of VLANs stored in it. This number is an u16 and gets multiplied by the size of the struct batadv_tvlv_tt_vlan_data (8 bytes). The size can therefore overflow the u16 used to store the tt_vlan_len. All additional safety checks to prevent out-of-bounds access of the TVLV buffer are invalid due to this overflow. Using size_t prevents this overflow and ensures that the safety checks compare against the actual buffer requirements.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://git.kernel.org/stable/c/0de12a4c4847f571d82a9cd96bc633eded41d7c6
- https://git.kernel.org/stable/c/1898273c5dc8148267ef9f97cd2517a2822350e7
- https://git.kernel.org/stable/c/3256c05d5a9db34346eaf20f52dddde984852d77
- https://git.kernel.org/stable/c/604bd5042fbcd1ab9f7cd98fd847ec017aeede8a
- https://git.kernel.org/stable/c/6222b443686525cb5a9b6a9cecf23b2e2ab23e2a
- https://git.kernel.org/stable/c/7319c0794f91be2734aac695794e7203606b49f8
- https://git.kernel.org/stable/c/7a581d9aaba8c82bd6177fa36b2588eea77f6e2b
- https://git.kernel.org/stable/c/d6ff4764ff784ede25f5c83a6f5883a74c93a5ea
Frequently asked
Is CVE-2026-72226 being actively exploited?
CVE-2026-72226 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.76%.
How severe is CVE-2026-72226?
CVE-2026-72226 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.76% probability of exploitation.
How do I fix CVE-2026-72226?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-72226 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.