Firmware dead lock when handling Socket Api Accept Service

When the Socket Api Accept service is used a firmware deadlock might occur under high load scenarios. In order to reproduce the issue, the backlog > 1 must be used.
Another problem occurs when an incomming connection is closed by the peer before the Accept Service has been used. In that case the connection socket will not be reported as closed an RecvFrom Service will not return with an error as expected.
Workarounds:

• For problem (1) setting backlog to 1 for an server socket will solve the problem
• For problem (2) application might implement a timeout for RecvFrom Service Confirmation and close the socket using Socket Close Service