asef I was also hoping someone else may give their thoughts
Yeah, no app should be able to cause memory corruption is kernel space, nor crash the kernel. That should be impossible. If it is possible, there is an issue with the OS itself, not the app.
asef I am considered a high risk target for this sort of thing but thought that GOS + good sense (hard earned) would make it difficult/expensive enough.
Using GrapheneOS absolutely helps to protect yourself if you are a high risk target, but as is evident from the logs here, it is not always enough.
asef I stopped using WhatsApp, reinstalled GOS and decided to only use Signal/Molly.
Although this is a good choice in general, I see nothing here that indicates WhatsApp caused the kernel space memory corruption. It was merely detected, by the kernel, while WhatsApp was the process running. There is no reason to suspect WhatsApp has anything to do with this memory corruption from the logs you have provided.
other8026 I'm confused. It's a crash that has only occurred while using WhatsApp, right?
Irrelevant what process it was that was currently running. It is a memory corruption in the kernel, and a kernel crash.
asef Could this be an indication of an exploited vulnerability.
Could be. Possible attack vectors that can have caused this memory corruption are vulnerabilities in Wifi driver, if you had Wifi enabled, 4G/5G drivers, if you had 4G/5G enabled, Bluetooth drivers, if you had Bluetooth enabled, but in that case you were probably quite close to the attacker physically, USB-C drivers, if you at any point connected your phone to a charger or other USB device during the current boot cycle. It could also be a malicious app you have installed, or an app that has been compromised, even WhatsApp, if your attacker likely have exploits against WhatsApp and know your phone number.
It is also quite possible it is just a bug in the kernel that caused some random memory corruption, and that this all is not a sign of an attack at all.
Still, any memory corruption in the kernel is a very serious issue, as it is possibly exploitable.
Unfortunately, the provided logs and information is not enough to find the cause of the memory corruption. MTE should have caught it, so I am confused why it didn't.