CVE-2026-63836

batman-adv: tp_meter: avoid divide-by-zero for dec_cwnd

N/A
Published: July 19, 2026 at 12:02 PM UTC
Updated: August 17, 2026 at 05:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: batman-adv: tp_meter: avoid divide-by-zero for dec_cwnd The cwnd is always MSS <= cwnd <= 0x20000000. But the calculation in batadv_tp_update_cwnd() assumes unsigned 32 bit arithmetics. ((mss * 8) ** 2) / (cwnd * 8) In case cwnd is actually 0x20000000, it will be shifted by 3 bit to the left end up at 0x100000000 or U32_MAX + 1. It will therefore wrap around and be 0 - resulting in: ((mss * 8) ** 2) / 0 This is of course invalid and cannot be calculated. The calculation should must be simplified to avoid this overflow: (mss ** 2) * 8 / cwnd It will keep the precision enhancement from the scaling (by 8) but avoid the overflow in the divisor. In theory, there could still be an overflow in the dividend. It is at the moment fixed to BATADV_TP_PLEN in batadv_tp_recv_ack() - so it is not an imminent problem. But allowing it to use the whole u32 bit range, would mean that it can still use up to 67 bits. To keep this calculation safe for 32 bit arithmetic, mss must never use more than floor((32 - 3) / 2) bits - or in other words: must never be larger than 16383.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.8 ≤ v < 5.10.2604.8 ≤ v < 5.15.2114.8 ≤ v < 6.1.1774.8 ≤ v < 6.12.954.8 ≤ v < 6.18.384.8 ≤ v < 6.6.1444.8 ≤ v < 7.1.34.8 ≤ v < 7.233a3bb4a3345bb511f9c69c913da95d4693e2a4e4.8
Vendor states this is fixed in 1381b021bf886b793fa5ffb895a8efae7ba0318f (fixed)
Vendor states this is fixed in 33ccd52f3cc9ed46ce395199f89aa3234dc83314 (fixed)
Vendor states this is fixed in 35264c4d46067d6312871488c810cef387f8c1f6 (fixed)
Vendor states this is fixed in 585616dab0aa9c45bc11b2c8082ca78533bc00e9 (fixed)
Vendor states this is fixed in 7d2a44bc6bbe39aed03c68864aa0e54e04a50278 (fixed)
Vendor states this is fixed in ac229c86e49fdb96d91f51bc2fa37a9c4f58c44f (fixed)
Vendor states this is fixed in cd74176cf1685f35a2e5f212d15748bbfecb53b6 (fixed)
Vendor states this is fixed in d08b69da40a101df1e28bfe1e8fa7a09ffa41107 (fixed)
Vendor states this is fixed in 4.8 (unaffected)
Vendor states this is fixed in 5.10.260 (unaffected)
Vendor states this is fixed in 5.15.211 (unaffected)
Vendor states this is fixed in 6.1.177 (unaffected)
Vendor states this is fixed in 6.12.95 (unaffected)
Vendor states this is fixed in 6.18.38 (unaffected)
Vendor states this is fixed in 6.6.144 (unaffected)
Vendor states this is fixed in 7.1.3 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusAWAITING ANALYSIS

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card