Envoy's `ProdClusterManagerFactory::allocateConnPool` function dereferences `transport socket options` when selecting an HTTP/3 connection pool without verifying if the pointer is null. Certain `LoadBalancerContext` implementations used by async-client, health-check, mirror, and synthetic calls may return no transport-socket options. When `auto config` and HTTP/3 are enabled, traffic routed through these contexts can cause an Envoy worker to crash.