Router reboot loop after latest update (3.10.1)

My router self-updated to 3.10.1 and rebooted during the night. When I woke up this morning I noticed that the wifi was intermittently on and off, then I checked the router and it was spontaneously rebooting itself every minute or so without warning. After countless tries I managed to capture the following dmesg output just before one of the reboots:

[   66.976406] ath10k_pci 0000:02:00.0: firmware crashed! (uuid a9c8d447-51a8-49f6-be19-b7187241568f)
[   66.985412] ath10k_pci 0000:02:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
[   66.985418] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[   66.986834] ath10k_pci 0000:02:00.0: firmware ver 10.2.4-1.0-00029 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 88595bb8
[   66.986853] ath10k_pci 0000:02:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[   66.986859] ath10k_pci 0000:02:00.0: htt-ver 2.1 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1
[   66.998896] ath10k_pci 0000:02:00.0: failed to get memcpy hi address for firmware address 4: -16
[   66.998903] ath10k_pci 0000:02:00.0: failed to read firmware dump area: -16
[   67.005881] ath10k_pci 0000:02:00.0: Copy Engine register dump:
[   67.011828] ath10k_pci 0000:02:00.0: [00]: 0x00057400  15  15   3   3
[   67.018298] ath10k_pci 0000:02:00.0: [01]: 0x00057800   3   3  70  71
[   67.024763] ath10k_pci 0000:02:00.0: [02]: 0x00057c00  45  33  32  33
[   67.031232] ath10k_pci 0000:02:00.0: [03]: 0x00058000   0   0   2   0
[   67.037696] ath10k_pci 0000:02:00.0: [04]: 0x00058400 382 374 241 201
[   67.044157] ath10k_pci 0000:02:00.0: [05]: 0x00058800  10  29 124 125
[   67.050622] ath10k_pci 0000:02:00.0: [06]: 0x00058c00  22  23  22  23
[   67.057083] ath10k_pci 0000:02:00.0: [07]: 0x00059000   0   1   0   1
[   67.087305] ath10k_pci 0000:02:00.0: failed to read hi_board_data address: -28
[   67.167941] ieee80211 phy0: Hardware restart was requested
[   67.259546] ath10k_pci 0000:02:00.0: failed to poke copy engine: -16
[   67.349511] ath10k_pci 0000:02:00.0: failed to poke copy engine: -16
[   67.439536] ath10k_pci 0000:02:00.0: failed to poke copy engine: -16
[   68.660363] ath10k_pci 0000:02:00.0: device successfully recovered
[   88.022159] ath10k_pci 0000:02:00.0: firmware crashed! (uuid 8894f9cd-f1f0-4b19-a478-35083cac453e)
[   88.031175] ath10k_pci 0000:02:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
[   88.031182] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[   88.032600] ath10k_pci 0000:02:00.0: firmware ver 10.2.4-1.0-00029 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 88595bb8
[   88.032618] ath10k_pci 0000:02:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[   88.032624] ath10k_pci 0000:02:00.0: htt-ver 2.1 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1
[   88.044663] ath10k_pci 0000:02:00.0: failed to get memcpy hi address for firmware address 4: -16
[   88.044669] ath10k_pci 0000:02:00.0: failed to read firmware dump area: -16
[   88.051656] ath10k_pci 0000:02:00.0: Copy Engine register dump:[   88.057601] ath10k_pci 0000:02:00.0: [00]: 0x00057400  15  15   3   3
[   88.064065] ath10k_pci 0000:02:00.0: [01]: 0x00057800  11  11 110 111
[   88.070534] ath10k_pci 0000:02:00.0: [02]: 0x00057c00  45  30  29  30
[   88.077000] ath10k_pci 0000:02:00.0: [03]: 0x00058000   9   9  11   9
[   88.083460] ath10k_pci 0000:02:00.0: [04]: 0x00058400  78  76  84  44
[   88.089928] ath10k_pci 0000:02:00.0: [05]: 0x00058800   7  14  45  46
[   88.096391] ath10k_pci 0000:02:00.0: [06]: 0x00058c00   3   4   3   4
[   88.102851] ath10k_pci 0000:02:00.0: [07]: 0x00059000   0   1   0   1
[   88.155702] ath10k_pci 0000:02:00.0: failed to read hi_board_data address: -28
[   88.236330] ieee80211 phy0: Hardware restart was requested
[   88.327953] ath10k_pci 0000:02:00.0: failed to poke copy engine: -16
[   88.417925] ath10k_pci 0000:02:00.0: failed to poke copy engine: -16
[   88.507908] ath10k_pci 0000:02:00.0: failed to poke copy engine: -16

I rolled back to the pre-update snapshot via schnapps and the reboots stopped.

An update: this is 100% reproducible in 3.10.2 and 3.10.3 as well.