Wide pointer metadata validity: check that the vtable is for the right trait #3497
Labels
I-misses-UB
Impact: makes Miri miss UB, i.e., a false negative (with default settings)
Comments
GuillaumeGomez
added a commit
to GuillaumeGomez/rust
that referenced
this issue
Apr 22, 2024
…=oli-obk Miri: detect wrong vtables in wide pointers Fixes rust-lang/miri#3497. Needed to catch the UB that rust-lang#123572 will start exploiting. r? `@oli-obk`
GuillaumeGomez
added a commit
to GuillaumeGomez/rust
that referenced
this issue
Apr 22, 2024
…=oli-obk Miri: detect wrong vtables in wide pointers Fixes rust-lang/miri#3497. Needed to catch the UB that rust-lang#123572 will start exploiting. r? ``@oli-obk``
rust-timer
added a commit
to rust-lang-ci/rust
that referenced
this issue
Apr 23, 2024
Rollup merge of rust-lang#124220 - RalfJung:interpret-wrong-vtable, r=oli-obk Miri: detect wrong vtables in wide pointers Fixes rust-lang/miri#3497. Needed to catch the UB that rust-lang#123572 will start exploiting. r? `@oli-obk`
github-actions bot
pushed a commit
that referenced
this issue
Apr 24, 2024
Miri: detect wrong vtables in wide pointers Fixes #3497. Needed to catch the UB that rust-lang/rust#123572 will start exploiting. r? `@oli-obk`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With rust-lang/rust#123572, rustc started assuming for UB purposes that a vtable pointer points to a vtabe that's sufficiently big for the given trait. Miri currently isn't able to check that UB.
The text was updated successfully, but these errors were encountered: