I'd say that this is a bit bizarre. I don't know all the ins and outs of ASAN and I'm not able to pick out what exactly its seeing in what you sent but I would say that if it's a compiled executable done in pure rust, by cargo. there shouldn't be anything to worry about.

Rustc is very aware of modules and crate boundaries (crates compiled to intermediate rlib files instead of native lib, as you mentioned) and mangles all non-externed symbols. Outside a dramatic compiler bug, with the way the compiler works, I don't see how there could be any overlaps or symbol mix-ups if that's what it's detecting.