### Security Approval Request * **How easily could an exploit be constructed based on the patch?**: not very easy. Freeing of an object must happen at the same time on 2 threads. Also this code is disabled on all channels therefore ther is only a small number of people actually affected. * **Do comments in the patch, the check-in comment, or tests included in the patch paint a bulls-eye on the security problem?**: Yes * **Which older supported branches are affected by this flaw?**: disabled on all beta and realease * **If not all supported branches, which bug introduced the flaw?**: Bug 1581637 * **Do you have backports for the affected branches?**: Yes * **If not, how different, hard to create, and risky will they be?**: not risky. This code is actually disabled * **How likely is this patch to cause regressions; how much testing does it need?**: not very likely, it only makes ref counting thread safe.
Bug 1618158 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
### Security Approval Request * **How easily could an exploit be constructed based on the patch?**: not very easy. Freeing of an object must happen at the same time on 2 threads. Also this code is disabled on all channels therefore there is only a small number of people actually affected. * **Do comments in the patch, the check-in comment, or tests included in the patch paint a bulls-eye on the security problem?**: Yes * **Which older supported branches are affected by this flaw?**: disabled on beta and release * **If not all supported branches, which bug introduced the flaw?**: Bug 1581637 * **Do you have backports for the affected branches?**: Yes * **If not, how different, hard to create, and risky will they be?**: not risky. This code is actually disabled * **How likely is this patch to cause regressions; how much testing does it need?**: not very likely, it only makes ref counting thread safe.