Last Modified: Jul 13, 2024
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
10.2.4, 11.5.1, 11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 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, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3
Opened: Mar 12, 2014 Severity: 3-Major
TMM may core after logging an error message like the following in the TMM log: notice panic: ../kern/xbuf.c:2273: Assertion "valid xfrag" failed. Analysis of the resulting TMM core may indicate that the original cause of the core was a segmentation fault resulting from an xbuf with a length discrepancy, in which the xfrag chain contains fewer bytes than the xbuf length indicates it should. In this case, the pointer to the next supposed xfrag in the chain is dereferenced, but since the pointer is NULL, as segmentation fault (SIGSEGV) occurs.
Traffic disrupted while tmm restarts.
The problem has been observed on BIG-IP 3600 and 3900 appliances running BIG-IP v10.2.4, but may occur under other conditions as well.
None known.
None