No it doesn't? This has nothing to do with memory safety. Its a logical error, which Rust physically cannot prevent.

This had nothing to do with Chrome, but rather Chromium.

>Considering that I'm using plain Chromium and not the branded Google Chrome, the channel will always be Channel::UNKNOWN. This also means that, unfortunately, the bug will not work on stable builds of Google Chrome since the release channel is set to the proper value there.

Malwares are going to be written in rust; What difference does it make? Also Its not memory based vulnerability but policy based vulnerability.

Did you even read the post?