That indicates that Greg Koah-Hartman has a very poor understanding of Rust and the _unsafe_ keyword. The bug can, in fact, exhibit undefined behavior and memory corruption.
His lack of understanding is unfortunate, to put it very mildly.
Or is this just a theoretical argument, "it is hypothetically possible to create a technically-spec-compliant Rust compiler that would compile this into dangerous machine code"? If so it should still be fixed of course, but if I'm patching my Linux kernel I'd rather know what the practical impact is.
To be fair, I'm not saying that Greg KH is definitely wrong; I'm only willing to claim that in the general case observing crashes due to corrupted pointers does not necessarily mean that there's no ability to actually exploit said corruption. Actual exploitability will depend on other factors as well, and I'm far from knowledgeable enough to say anything on the matter.
[0]: https://projectzero.google/2014/08/the-poisoned-nul-byte-201...
Same thing is true about modern C++, and as an added bonus, it's far more straightforward to rewrite legacy C code into modern C++ than it is to rewrite it in Rust, and you can do so without compromising existing support for any architectures thanks to GCC (unlike Rust, which relies on LLVM-based rustc), yet there's still a baffling blanket ban on C++ in the kernel. I say "baffling," since it's unjustifiable on technical grounds, but it's easily explained as a mix of Linus by proxy (Greg) being too proud to walk back his infamous vituperative denunciation of the language (even though it's since evolved considerably), and Rust zealots being so numerous, motivated, organized, and also mentally and hormonally unstable enough that it's just not worth the effort to resist them. If C++ developers were the types to threaten self-harm when they didn't get their way, C++ would probably be in the kernel too.