Bug ID 1030185: TMM may crash when looking up a persistence record using "persist lookup" iRule commands

Last Modified: Feb 07, 2024

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 16.0.1, 16.0.1.1, 16.0.1.2

Fixed In:
17.0.0, 16.1.4, 15.1.9

Opened: Jun 30, 2021

Severity: 2-Critical

Symptoms

Tmm may crash with a SIGSEGV when looking up a persistence record in an iRule when using the "any" flag

Impact

Traffic disrupted while tmm restarts.

Conditions

-- The persistence entry exists on a virtual server other than the virtual server the iRule is configured on. -- The iRule contains [persist lookup source_addr "[IP::client_addr] any"]

Workaround

Discontinue the use of the "any" flag in the persist lookup iRule.

Fix Information

TMM no longer crashes

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips