Same problem here on an iPhone 17 Pro Max 256GB, purchased on September 27th.
I thought it might be a corrupted backup from my previous iPhone. I contacted Apple, shared the panic logs, and they themselves checked my phone via screen sharing and ran a diagnostic. They confirmed a bug, but didn't specify whether it was, hardware or software.
They recommended putting it into DFU mode and restoring. I did so, and after the restore, it was on iOS 26.1 beta and reverted to iOS 26.0.1. It didn't shut down anymore, and I started downloading all the apps since I didn't use the backup from the previous one.
I thought I had fixed it. I used it on my home Wi-Fi, and it lasted almost 10 hours without rebooting, but today when I tried to connect to CarPlay, it rebooted.
The worst part is that I live in Brazil and here the stores don't exchange the device for a new one (not that it will apparently solve the problem), but they push you to 'fix' it within an estimated period of 30 days without the device (this local policy is not easy...).
At the moment I'm hoping it's a software problem, but I have no hope that it will be solved with IOS 26.1, given that I was already using it when this problem started.
Finally, just to share a part of the full panic that appears at the beginning in case it helps someone who is going through the same situation:
"product" : "iPhone18,2",
"kernel" : "Darwin Kernel Version 25.0.0: Thu Sep 25 15:05:47 PDT 2025; root:xnu-12377.2.9~1\/RELEASE_ARM64_T8150",
"socRevision" : "11",
"panicString" : "panic(cpu 1 caller 0xfffffe00440cc1ac): ANS2 SERROR Exception class=0x2f (SError interrupt), IL=1, iss=0 - Cmd(11)\nRTKit: root@Aug 02 2025@20:10:33~.release - Client: t8150.release-AppleStorageFirmware-2914.0.121~874~2914.0.121~874\n!UUID: a1000010-2140-1ed5-a178-80d201401ed5\nASLR slide: 0x0000000000504000\nTime: 0x000000f17176d78f\n\nFaulting task stack frame:\nWrong frame size for ARMv8. Got 840 bytes, expected 828\n Exception class=0x2f (SError interrupt), IL=1, iss=0\n
Take care everyone,
Fabrício.