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

Last Modified: Sep 13, 2023

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

Known Affected Versions:
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 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
13.0.0, 11.6.1 HF1

Opened: Jan 28, 2016

Severity: 2-Critical

Related 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

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips