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
After a memory is grown a view must not be used anymore.
However, it is possible to do this in safe code and instead of producing an error or panicking this results in a segfault. So there is a soundness issue with the interaction of Memory::grow and Memory::view.
Describe the bug
https://docs.rs/wasmer/3.1.0/wasmer/struct.MemoryView.html documents:
However, it is possible to do this in safe code and instead of producing an error or panicking this results in a segfault. So there is a soundness issue with the interaction of
Memory::grow
andMemory::view
.wasmer v3.1.0 | rustc 1.66.1 (90743e729 2023-01-10) | x86_64
Steps to reproduce
Expected behavior
One of the following:
Store
borrowed for the lifetime ofMemoryView
.Actual behavior
Access to freed memory in safe code. Segfault.
The text was updated successfully, but these errors were encountered: