[asterisk-bugs] [JIRA] (ASTERISK-30363) Crash during srtp session

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-30363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261093#comment-261093 ] 

Asterisk Team commented on ASTERISK-30363:
------------------------------------------

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

> Crash during srtp session
> -------------------------
>
>                 Key: ASTERISK-30363
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30363
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_rtp_asterisk
>    Affects Versions: 18.10.1
>         Environment: Debian 11
>            Reporter: Vitezslav Novy
>            Assignee: Vitezslav Novy
>         Attachments: bt.txt
>
>
> On one of our sites asterisk crashed once with attached backtrace.
> I have core dump available and I noticed that in __rtp_recvfrom() rtp->dtls.ssl is NULL
> It points to some race because there is a test in the function which returns immediately when rtp->dtls.ssl == NULL.  Probably short unlock/lock sequence allowing timer manipulation is the reason. 
> I guess it is a race with ast_rtp_dtls_stop() which destroys ssl and sets ssl to NULL.
> I created a patch for us which checks rtp->dtls,ssl again after unlock/lock sequence. I cannot afford a lawyer so I do not attach it



--
This message was sent by Atlassian JIRA
(v6.2#6252)