Last Modified: Mar 25, 2025
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 17.0.0, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.5.0
Opened: Nov 29, 2023 Severity: 3-Major
When iRule is using badly crafted regexp or regsub command, sometimes large regex compilation may lead to TMM core. - Multiple clock advances will be logged in tmm logs. - A message similar to the one below will be logged in tmm logs: notice sod[9938]: 01140041:5: Killing tmm.0 pid <pid of tmm>.
Traffic disrupted while tmm restarts.
- iRules using regexp or regsub command with large expression
Update iRule to avoid using regex or regsub with large expressions. either by 1. setting an upper-limit on the permitted size for regex expression or 2. rewrite the iRule to avoid the use of 'regsub'.
None