vpnkit crashing on intel macOS 12.6.1 with EXC_BAD_ACCESS (SIGSEGV)

Hopefully Apple sends you crash reports.
Docker for Mac 4.13.0 (89412) on my recently upgraded Monterrey macOS started getting frequent SIGSEGV crashes.
FortiClient and Sophos are also running.

Translated Report (Full Report Below)
-------------------------------------

Process:               com.docker.vpnkit [74598]
Path:                  /Applications/Docker.app/Contents/Resources/bin/com.docker.vpnkit
Identifier:            com.docker.vpnkit
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        com.docker.backend [58194]
Responsible:           Docker [58193]
User ID:               481229023

Date/Time:             2022-10-28 19:15:45.4584 -0500
OS Version:            macOS 12.6.1 (21G217)
Report Version:        12
Bridge OS Version:     7.0 (20P411)
Anonymous UUID:        8282D147-87A1-6BE6-51E1-91E072DC65C3

Sleep/Wake UUID:       7A4973E8-63B1-4A28-A4A2-01993E992E10

Time Awake Since Boot: 100000 seconds
Time Since Wake:       32722 seconds

System Integrity Protection: enabled

Crashed Thread:        3

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       UNKNOWN_0xD at 0x0000000000000000
Exception Codes:       0x000000000000000d, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [74598]

VM Region Info: 0 is not in any region.  Bytes before following region: 4500197376
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->  
      __TEXT                      10c3b9000-10cce1000    [ 9376K] r-x/r-x SM=COW  ...docker.vpnkit

Kernel Triage:
VM - Compressor failed a blocking pager_get
VM - Compressor failed a blocking pager_get
VM - Compressor failed a blocking pager_get
VM - Compressor failed a blocking pager_get
VM - Compressor failed a blocking pager_get


Thread 0::  Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	    0x7ff80bfe8d5a __select + 10
1   com.docker.vpnkit             	       0x10cb1c46e unix_select + 814
2   com.docker.vpnkit             	       0x10c474691 camlLwt_engine__fun_2758 + 33
3   com.docker.vpnkit             	       0x10c4741ad camlLwt_engine__fun_2681 + 269
4   com.docker.vpnkit             	       0x10c4741ad camlLwt_engine__fun_2681 + 269
5   com.docker.vpnkit             	       0x10c4741ad camlLwt_engine__fun_2681 + 269
6   com.docker.vpnkit             	       0x10c4741ad camlLwt_engine__fun_2681 + 269
7   com.docker.vpnkit             	       0x10c4741ad camlLwt_engine__fun_2681 + 269
8   com.docker.vpnkit             	       0x10c4741ad camlLwt_engine__fun_2681 + 269
9   com.docker.vpnkit             	       0x10c4741ad camlLwt_engine__fun_2681 + 269
10  com.docker.vpnkit             	       0x10c4741ad camlLwt_engine__fun_2681 + 269
11  com.docker.vpnkit             	       0x10c4741ad camlLwt_engine__fun_2681 + 269

Let me know if you need fuller details.

Start with the supplied crash report for /Applications/Docker.app/Contents/Resources/bin/com.docker.vpnkit, especially crashed Thread 3 and the OCaml Lwt stack context. Reproduce on Intel macOS 12.6.1 with Docker for Mac 4.13.0 and the reported security clients; done means the vpnkit process no longer exits with EXC_BAD_ACCESS.