> > # echo "install algif_aead /bin/false" > /etc/modprobe.d/disable-algif.conf > > # rmmod algif_aead > > Brad Spengler has been pointing out that this won't work on a few common > enterprise kernels where CONFIG_CRYPTO_USER_API_AEAD=y (rather than m).
An initial test of adding: initcall_blacklist=algif_aead_init to the kernel command line and rebooting seems to block the exploit. Cheers.
