CVE-2026-98432 also applies to non-MPTCP connections. That's why disabling MPTCP was actively discouraged as a workaround (low level firewalls that clear all options do work, though, and they'd also work fine with Caddy).
Plus, Caddy itself wasn't vulnerable in this specific case. There wasn't much the Caddy folks could've done to protect against a problem in the Linux kernel itself.