-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AddressSanitizer: NPE read in multithreading mode #176
Comments
FYI, we collected several other pocs with different crashing backtraces here. |
@hongxuchen Thank you for the report! |
@lexborisov my pleasure! |
Hi @lexborisov , I had a quick review of the source code, it seems to relevant with the data race on |
Thanks for the work you've done! P.S.: There are no such problems in the lexbor project: the speed is the same, there are no threads, it consumes less resources, selectors will appear soon. |
@lexborisov Great! Will try lexbor 👌 |
When fuzzing the AddressSanitizer hardened
callback_tree_node_high_level
, we found several vulnerabilities/crashes due to multithreading.A sample proof-of-crash (poc) file (zipped) is:
NPE_r__mchar_async.c:656_1.html.zip
with the error message like:
In case it is not easily reproducible, we use the following command:
We will provide other pocs later.
The text was updated successfully, but these errors were encountered: