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

[Ben Smithurst (JIRA)]

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

Ben Smithurst commented on ASTERISK-24521:
------------------------------------------

We do have some modifications - I wouldn't expect any of them to cause this but you never know.  We have since observed the pointer being a corrupt pointer in other ways rather than null, so it could be something being free'd too early and overwritten or something.  We've now updated to 11.15.0 anyway so it might be worth closing this and we'll look into it further at our end if it carries on with the latest version.

> [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)