You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The above fifo_hidmsg_add is ultimately called from USB_IRQHandler which seems to run directly from interrupt context (see startup_stm32l432xx.s).
However, as best I can tell (FIFO functions defined here), neither fifo_hidmsg_add nor fifo_hidmsg_take (or its usage in the code) are guarding against interrupts.
Posting as an issue because I do not believe this represents a security vulnerability, but if a HID request comes in while fifo_hidmsg_take is running, I suspect it will bork the FIFO state.
The text was updated successfully, but these errors were encountered:
While looking through the code I found a possible race condition in usbd_hid.c:
The above
fifo_hidmsg_add
is ultimately called fromUSB_IRQHandler
which seems to run directly from interrupt context (see startup_stm32l432xx.s).However, as best I can tell (FIFO functions defined here), neither
fifo_hidmsg_add
norfifo_hidmsg_take
(or its usage in the code) are guarding against interrupts.Posting as an issue because I do not believe this represents a security vulnerability, but if a HID request comes in while
fifo_hidmsg_take
is running, I suspect it will bork the FIFO state.The text was updated successfully, but these errors were encountered: