Bug ID 746877: Omitted check for success of memory allocation for DNSSEC resource record

Last Modified: Oct 06, 2020

Bug Tracker

Affected Product:  See more info
BIG-IP DNS(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.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 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.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5

Fixed In:
15.0.0, 14.1.0.6, 14.0.0.5, 13.1.1.5, 12.1.4.1

Opened: Oct 15, 2018
Severity: 3-Major

Symptoms

The TMM may panic from SIGABRT while logging this message: ./rdata.c:25: ldns_rdf_size: Assertion `rd != ((void *)0)' failed.

Impact

TMM panic and subsequent interruption of network traffic.

Conditions

During memory stress while handling DNSSEC traffic.

Workaround

Keeping the workload within normal ranges reduces the probability of encounter.

Fix Information

The system now checks for success of memory allocation for DNSSEC resource record, so this issue no longer occurs.

Behavior Change