Are you exposed to Copy Fail?

A 9-year-old Linux kernel bug, disclosed April 29 2026, hands root access to any local user on every major distribution. Answer four quick questions and we'll tell you what to do — no scanning, no data sent anywhere.

Step 1 of 4

Which Linux distribution are you running?

Ubuntu / Debianapt-based AlmaLinux / CentOS / Fedora / RHEL / Rockydnf or yum Amazon LinuxAWS EC2 default image SUSE / openSUSEzypper Other / not sureAlpine, Arch, custom, managed hosting, etc.

Step 2 of 4

When did you last apply kernel updates and reboot?

After May 1, 2026Updated and rebooted in the last few days Between mid-April and end of April 2026Patched but possibly before your distro shipped the fix Before April 2026Or you don't remember Managed hosting — someone else does ite.g. WebWorld manages the server for me

Step 3 of 4

Who else can run code on this server?

Tick everything that applies.

Multiple users have shell accessSSH, sudo accounts, dev team, customers Self-hosted CI/CD runnerGitHub Actions self-hosted, GitLab Runner, Jenkins, etc. Runs containersDocker, Kubernetes, Podman — especially with untrusted images Public PRs trigger builds hereOpen-source repo with self-hosted runners None of the above — I'm the only userSingle-tenant box, only I have shell access

Step 4 of 4

Have you blocked the `algif_aead` kernel module?

If you don't know, choose "Not sure". Most servers have not.

Yes, blocked via modprobe.dSaw the mitigation guidance and applied it No / not sureDefault configuration

Report a Bug • Request a Feature • Contact Us

Are you exposed to Copy Fail?

Which Linux distribution are you running?

When did you last apply kernel updates and reboot?

Who else can run code on this server?

Have you blocked the algif_aead kernel module?

Have you blocked the `algif_aead` kernel module?