Bug ID 570363: Potential segfault when MRF messages cross from one TMM to another.

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
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, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4

Fixed In:
13.0.0, 11.6.1 HF1

Opened: Jan 28, 2016
Severity: 2-Critical
Related AskF5 Article:
K21694039

Symptoms

Potential segfault when Message Routing Framework (MRF) messages cross from one TMM to another.

Impact

It is possible for the message object to be removed before the asynchronous operation completes. If this occurs, a segfault may occur and the system might restart.

Conditions

This issue occurs when MRF messages travel from one TMM to another, and an asynchronous operation also occurs (like persistence).

Workaround

None.

Fix Information

This release corrects the issue of potential segfault occurring when MRF messages cross from one TMM to another.

Behavior Change