Bug ID 734539: The IKEv1 racoon daemon can crash on multiple INVALID-SPI payloads

Last Modified: Nov 22, 2021

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,,,,,, 12.1.4,, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 14.0.0,,,,,, 14.0.1

Fixed In:
14.1.0,, 13.1.3, 12.1.5

Opened: Jul 12, 2018
Severity: 2-Critical


When an IKEv1 peer sends an INVALID-SPI payload, and BIG-IP system cannot find the phase-two Security Association (SA) for that SPI but can find phase-one SA involved; the racoon daemon may crash if there are additional INVALID-SPI payloads afterward.


The v1 racoon daemon cores, interrupting traffic until new tunnels can be established after racoon restarts.


-- An INVALID-SPI notification is received. -- That phase-two SA is already gone. -- The phase-one parent SA is still around. -- Subsequent notification INVALID-SPI payloads involve the same phase-one SA.


There is no workaround at this time.

Fix Information

The system no longer destroys the parent phase-one SA when an INVALID-SPI notification cannot find the target phase-two SA, so this issue does not occur.

Behavior Change