[asterisk-bugs] [JIRA] (ASTERISK-24521) [patch] Segfault due to null pointer in ast_bridged_channel

[Matt Jordan (JIRA)]

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

Matt Jordan commented on ASTERISK-24521:
----------------------------------------

If you are running a modified version of Asterisk, there's a good chance there isn't anything we can do to help. If you can find a way to reproduce the issue reliably - or if you can narrow down the problem - that would help a lot. As it is, I don't see how the patch provided would alleviate the problem, or how an {{ast_channel_tech}} is going to become a garbage pointer. I _suppose_ that could happen if you are unloading a channel driver while a call using that channel driver is in progress - although, all channel drivers will also bump their module ref count to prevent that very thing from occurring.

I'll suspend this for now, barring more information.

> [patch] Segfault due to null pointer in ast_bridged_channel
> -----------------------------------------------------------
>
>                 Key: ASTERISK-24521
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24521
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Channels
>    Affects Versions: 11.8.1
>            Reporter: Ben Smithurst
>         Attachments: ast_bridged_channel.diff, backtrace.txt
>
>
> We have observed a crash in ast_bridged_channel due to a null pointer.  We do not know at present how to reproduce it, it is something we haven't really seen before but then saw several times in a single day.
> The cause appears to be a bridged channel existing without a 'tech' field, so the ast_bridged_channel function dereferences a null pointer, the fix is quite simple and seems to work for us, we've seen no further occurences of the crash.
> *Hopefully* I still have the backtrace/core file, but if not, as I say we don't know how to reproduce it, apologies.



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