Yes. On systems where SCTP is built as a loadable module rather than built into the kernel, unloading the sctp module and preventing it from being loaded should mitigate exploitation of this issue.
mitigation, for example: sudo sh -c "printf 'install sctp /bin/false\n' > /etc/modprobe.d/block-CVE-2026-64564.conf" sudo rmmod sctp Fourie Solar Designer <[email protected]> 于2026年8月7日周五 04:04写道： > > Hi, > > Thank you for bringing this to oss-security. > > On Thu, Aug 06, 2026 at 07:33:31PM +0800, Fourie Zhang wrote: > > - Rocky Linux 9 / RHEL 9-family target, vendor 5.14 kernel (SCTP loaded) > > On these distros, the SCTP module is not part of a typical install, but > is in the kernel-modules-extra subpackage. > > Further, that subpackage includes module blacklist files with: > > blacklist sctp > blacklist sctp_diag > > which prevents unprivileged autoload of these modules on demand. > > So the sysadmin would have to explicitly install kernel-modules-extra > and load the SCTP module to expose this vulnerability, meaning that in > practice it would only be exposed on systems that actually use SCTP. > > Of course, exposure likely varies by distro. The above is just about > the RHEL family distros with their recent kernels. > > Alexander
