11–14 of 14 posts
Yeah run a highly privileged, node-level workload by an Internet stranger to mitigate against a kernel vulnerability. No thanks. In any case, this unloads the module which does nothing if it's compiled into the kernel as in GKE.
just plug it in and click the .exe file
Blacklisting a kernel module only prevents modprobe from loading it automatically. modprobe by name still works, even if the module is blacklisted, and so does insmod and the syscalls they use. The author is way above their head and thinks that because they can write Copilot prompts they can write security critical software.
sudo rm "$(modinfo -n algif_aead)"
modinfo -n algif_aead && sudo mv "$(modinfo -n algif_aead)" "$(modinfo -n algif_aead)_"Yeah run a highly privileged, node-level workload by an Internet stranger to mitigate against a kernel vulnerability. No thanks. In any case, this unloads the module which does nothing if it's compiled into the kernel as in GKE.
here i've got this USB that will fix any vulns on your system. just plug it in and click the .exe file
no sudo permissions required, it takes care of that nonsense.
Blacklisting a kernel module only prevents modprobe from loading it automatically. modprobe by name still works, even if the module is blacklisted, and so does insmod and the syscalls they use. The author is way above their head and thinks that because they can write Copilot prompts they can write security critical software.
Agreed. There is a way but I would never recommend it to anyone. Showing just for completeness sake in the event anyone else suggests it but do not do this and certainly never put it in a config file or "bad things will happen ©2009-2026".
# rmmod the module of concern first, then if that exits with the correct exit code:
sysctl -w kernel.modules_disabled = 1
sysctl -w kernel.kexec_load_disabled = 1