CVE-2024-35982batman-adv: Avoid infinite loop trying to resize local TT

Description

In the Linux kernel, the following vulnerability has been resolved: batman-adv: Avoid infinite loop trying to resize local TT If the MTU of one of an attached interface becomes too small to transmit the local translation table then it must be resized to fit inside all fragments (when enabled) or a single packet. But if the MTU becomes too low to transmit even the header + the VLAN specific part then the resizing of the local TT will never succeed. This can for example happen when the usable space is 110 bytes and 11 VLANs are on top of batman-adv. In this case, at least 116 byte would be needed. There will just be an endless spam of batman_adv: batadv0: Forced to purge local tt entries to fit new maximum fragment MTU (110) in the log but the function will never finish. Problem here is that the timeout will be halved all the time and will then stagnate at 0 and therefore never be able to reduce the table even more. There are other scenarios possible with a similar result. The number of BATADV_TT_CLIENT_NOPURGE entries in the local TT can for example be too high to fit inside a packet. Such a scenario can therefore happen also with only a single VLAN + 7 non-purgable addresses - requiring at least 120 bytes. While this should be handled proactively when: * interface with too low MTU is added * VLAN is added * non-purgeable local mac is added * MTU of an attached interface is reduced * fragmentation setting gets disabled (which most likely requires dropping attached interfaces) not all of these scenarios can be prevented because batman-adv is only consuming events without the the possibility to prevent these actions (non-purgable MAC address added, MTU of an attached interface is reduced). It is therefore necessary to also make sure that the code is able to handle also the situations when there were already incompatible system configuration are present.

Timeline

Scores

EPSS (exploitation in 30 days)

0.26% · top 82% of all CVEs (13 Nov 2026)

CISA SSVC

Exploitation: none · Automatable: no · Technical impact: partial

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.1.

Affected products

• Linux · Linux

  • affected a19d3d85e1b854e4a483a55d740a42458085560d – < 04720ea2e6c64459a90ca28570ea78335eccd924
  • affected a19d3d85e1b854e4a483a55d740a42458085560d – < b3ddf6904073990492454b1dd1c10a24be8c74c6
  • affected a19d3d85e1b854e4a483a55d740a42458085560d – < 70a8be9dc2fb65d67f8c1e0c88c587e08e2e575d
  • affected a19d3d85e1b854e4a483a55d740a42458085560d – < 87b6af1a7683e021710c08fc0551fc078346032f
  • affected a19d3d85e1b854e4a483a55d740a42458085560d – < 3fe79b2c83461edbbf86ed8a6f3924820ff89259
  • affected a19d3d85e1b854e4a483a55d740a42458085560d – < 4ca2a5fb54ea2cc43edea614207fcede562d91c2
  • affected a19d3d85e1b854e4a483a55d740a42458085560d – < ca54e2671548616ad34885f90d4f26f7adb088f0
  • affected a19d3d85e1b854e4a483a55d740a42458085560d – < b1f532a3b1e6d2e5559c7ace49322922637a28aa

• Linux · Linux

  • affected 3.13
  • unaffected < 3.13
  • unaffected 4.19.313 – ≤ 4.19.*
  • unaffected 5.4.275 – ≤ 5.4.*
  • unaffected 5.10.216 – ≤ 5.10.*
  • unaffected 5.15.156 – ≤ 5.15.*
  • unaffected 6.1.87 – ≤ 6.1.*
  • unaffected 6.6.28 – ≤ 6.6.*
  • unaffected 6.8.7 – ≤ 6.8.*
  • unaffected 6.9 – ≤ *

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• EUVD EUVD-2024-35700 (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2024-35982](https://cveledger.app/badge/CVE-2024-35982.svg)](https://cveledger.app/cve/CVE-2024-35982)

Record last updated 15 Oct 2026, 00:41 UTC.