Skip to content

Comments

Avoid potential deadlocks#1373

Merged
Mr-Dave merged 1 commit intoMotion-Project:masterfrom
Mr-DaveDev:20210729_mutexlock
Jul 31, 2021
Merged

Avoid potential deadlocks#1373
Mr-Dave merged 1 commit intoMotion-Project:masterfrom
Mr-DaveDev:20210729_mutexlock

Conversation

@Mr-DaveDev
Copy link
Contributor

Closes #1363
Closes #1364

Thanks @/jenny-cheung

@Mr-Dave Mr-Dave merged commit dce76ee into Motion-Project:master Jul 31, 2021
@Mr-DaveDev Mr-DaveDev deleted the 20210729_mutexlock branch August 7, 2021 23:43
@jenny-cheung
Copy link

Hi, any security impacts for these lock leak issues? I think it is possible to trigger a DoS induced by deadlocks due to reacquiring the same lock. Could we request CVE IDs for these? Thanks so much

@Mr-Dave
Copy link
Member

Mr-Dave commented Oct 16, 2021

I don't really see any way that a DoS could be possible.

@jenny-cheung
Copy link

Many lock leaks have lead to security issues(e.g., DoS) like CVE-2020-12771, CVE-2015-8340, CVE-2014-3657, because it is easy to result in reacquiring the same lock.

But it depends. Thanks for your reply.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Potential error(e.g., deadlock) due to the unreleased lock&bktr_mutex Potential error(e.g., deadlock) due to the unreleased lock&netcam->mutex

3 participants