Last Modified: Jul 18, 2026
Affected Product(s):
BIG-IP APM
Known Affected Versions:
11.5.4, 11.5.4 hf1, 11.5.4 hf2, 11.5.4 hf3, 11.5.4 hf4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.0 hf1, 11.6.0 hf2, 11.6.0 hf3, 11.6.0 hf4, 11.6.0 hf5, 11.6.0 hf6, 11.6.0 hf7, 11.6.0 hf8, 11.6.1, 11.6.1 hf1, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 12.0.0, 12.0.0 hf1, 12.0.0 hf2, 12.0.0 hf3, 12.0.0 hf4, 12.1.0, 12.1.0 hf1, 12.1.0 hf2, 12.1.1, 12.1.1 hf1, 12.1.1 hf2, 12.1.2, 12.1.2 hf1, 12.1.2 hf2, 12.1.3, 12.1.3.1, 13.0.0, 13.0.0 hf1, 13.0.0 hf2, 13.0.0 hf3
Fixed In:
13.1.0, 13.0.1, 12.1.3.2, 11.6.3
Opened: Mar 06, 2017 Severity: 2-Critical Related Article:
K64131101
When APM resumes an iRule event from an asynchronous session data lookup, the resumption fails due to a bad memory access resulting in a crash.
Traffic disrupted while tmm restarts.
The following must be true for this to happen: - APM provisioned and licensed. - Use of APM iRule events. - Session data lookup from iRule events.
None.
Access to an invalid or stale Access session result from custom iRules no longer causes TMM crash.