Hacker News Reader

There is no bounds checking inside WebAssembly itself, as it lacks the concept of fat pointers.

So you can still trigger memory corruption if the WebAssembly was generated from languages like C and C++.

Again, not in any way that can cause instability to the kernel differently from running the same program in user space.

As community should strive for more secure software instead of hand waving security issues.

I never argued that it shouldn't, just that the issues you're raising aren't relevant to the security of running wasm in kernel space.