-
Notifications
You must be signed in to change notification settings - Fork 711
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
crash in pcsc_transmit -> sc_apdu_log -> sc_hex_dump #3138
Comments
jeffallen
changed the title
sc_apdu_get_octets can apparently return SC_SUCCESS, but leave buf and size wrong
crash in pcsc_transmit -> sc_apdu_log -> sc_hex_dump
May 8, 2024
I put a workaround in place for #3139 and this crash stopped. So I'm closing this in favor of the other issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem Description
I have a repeatable crash of Firefox caused by using a PKCS11 card, then suspending, removing the card, and resuming.
I managed to capture this backtrace:
The code leading up to line 326 is:
This is why I suspect that sbuf and/or ssize are not valid, causing a crash inside of sc_apdu_log.
On the other hand, I was able to check that sbuf is set to a reasonable pointer, and ssize was 9. So I'm editing the title of this -- I have a different theory, about recursion and stack depth.
Proposed Resolution
Don't crash. :)
No, seriously, I'm going to keep digging and send a PR. Just wanted to write down what I found so far so people know what I'm working on.
Steps to reproduce
I have a repeatable crash of Firefox caused by using a PKCS11 card, then suspending, removing the card, and resuming.
The text was updated successfully, but these errors were encountered: