You can have memory corruption in pure Go code, too.

Uh huh. That's where all the Go memory corruption vulnerabilities come from!

Nobody claimed otherwise. You're interacting with a kernel that invented its own programming language based on macros, after all, instead of relying on a compiler for that.

What could go wrong with this, right?

/s