Last Modified: Oct 07, 2026
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
17.1.2.2, 17.1.3, 17.1.3.1, 17.1.3.2, 17.1.3.4, 17.1.3.5, 17.5.1.3, 17.5.1.4, 17.5.1.5, 17.5.1.6, 17.5.1.8, 17.5.1.9
Opened: Mar 30, 2026 Severity: 4-Minor
When the BIG-IP system can't create the internal flow for a new HTTP/2 stream in HTTP/2 gateway mode, the memory set aside for that stream's HTTP request data is never freed. Each failed stream setup leaks a small amount of TMM memory. Over time, TMM memory use keeps growing
TMM memory use grows over time. If the failures go on long enough, TMM can run out of memory. Traffic may then be disrupted, or TMM may restart, and traffic is interrupted while it does
- A virtual server uses an HTTP/2 profile in gateway mode - TMM is low on memory or resources, so creating the internal flow for a new HTTP/2 stream fails - Clients keep opening new HTTP/2 streams while those failures continue
None. To reduce the risk, avoid conditions that put TMM under memory pressure, and watch TMM memory usage (for example, with tmctl -a memory_usage_stat or tmsh show sys memory) on systems that use HTTP/2 gateway mode
None