You don't run Linux. You run Windows laptops, an iPhone and Microsoft 365. So why does a Linux bug matter to you?
Because something in your business almost certainly runs Linux underneath. Your website's server. The cloud server your line-of-business app lives on. Quite possibly the storage box in the closet, the firewall, or the VPN box your staff use from home. You just never see it.
In spring 2026, three serious Linux kernel bugs landed within about three weeks of each other. The newest, Fragnesia, is the one this post was written about.
The quick answer
- Make a list of everything you have that runs Linux: web hosting, cloud servers, storage boxes (NAS), firewalls, VPN appliances.
- For servers you or your IT person manage: install the kernel update and reboot. The fix doesn't take effect until you do.
- For appliances and hosting: ask the vendor or host one question, in writing: "Are you patched for CVE-2026-46300 (Fragnesia), and the Dirty Frag and Copy Fail CVEs?"
- If a server can't be updated yet, ask your IT person about the temporary mitigation below.
What happened, with dates
The three bugs are in the Linux kernel, the core of the operating system. All three let someone who already has a low-level account on a machine turn it into root, the Linux word for full administrator control.
Here's the timeline, from Ubuntu's security advisories:
Name | CVE | Made public |
|---|---|---|
Copy Fail | CVE-2026-31431 | April 29, 2026 |
Dirty Frag | CVE-2026-43284 and CVE-2026-43500 | May 7, 2026 |
Fragnesia | CVE-2026-46300 | Mid-May 2026 |
Copy Fail is a flaw in a kernel crypto module called algif_aead. Ubuntu said a published exploit worked against it (Ubuntu: Copy Fail fixes available). The U.S. Cybersecurity and Infrastructure Security Agency added it to its Known Exploited Vulnerabilities catalog on May 1, 2026. That catalog only lists bugs CISA has evidence attackers are actually using.
Dirty Frag is a pair of bugs in how the kernel handles encrypted network traffic (IPsec) and a file-sharing protocol called RxRPC (Ubuntu: Dirty Frag fixes available).
Fragnesia sits in the same part of the kernel as Dirty Frag, but it's a separate bug with its own fix. Ubuntu rates it High priority, CVSS score 7.8, with the note "trivial local privilege escalation," and says it could also let an attacker break out of a container (Ubuntu: CVE-2026-46300). Being patched for Dirty Frag doesn't automatically mean you're patched for Fragnesia. Check for both CVE numbers.
As of CISA's catalog dated October 8, 2026, Copy Fail is listed as exploited. Dirty Frag and Fragnesia are not. That doesn't make them safe to ignore. Ubuntu rates Fragnesia as "trivial" to exploit for anyone who already has a foothold, and Ubuntu has since shipped fixed kernels for all three.
Does this affect your business?
Here's the deal. These are local bugs. An attacker needs some way to run code on the machine first: a stolen login, a hacked website plugin, a malicious app in a container. They're the second step of a break-in, not the first.
So the risk depends on who can run code on the box:
- Shared web hosting and multi-user servers: highest risk. Lots of accounts on one machine. This is your host's job to patch, but you should ask.
- Cloud servers and containers (anything running Docker or Kubernetes): high. Ubuntu says these bugs may allow escaping a container.
- A server only your IT person logs into: lower, but still patch it. If anyone ever steals that login, this turns a foothold into full control.
- Appliances (NAS, firewall, VPN box): depends on the vendor. You can't patch the kernel yourself; you wait for a firmware update. Check the vendor's security advisory page for the CVE numbers.
Ordinary Windows PCs and Macs don't run the Linux kernel, so these bugs don't apply to them.
How to fix it
On Ubuntu servers
This is the step for whoever manages the server. Check the running kernel:
uname -r
Then update and reboot:
sudo apt update && sudo apt upgrade
sudo reboot
Ubuntu lists the Fragnesia fix in kernel 6.8.0-124.124 for Ubuntu 24.04 LTS and 5.15.0-181.191 for 22.04 LTS, as of its advisory page updated August 27, 2026 (Ubuntu: CVE-2026-46300). If uname -r after the reboot shows an older number, the update didn't take.
Other Linux distributions (Red Hat, Debian, SUSE and so on) publish their own fixed versions. Search the distribution's security tracker for the CVE number.
On hosting, cloud and appliances
Send one message to each provider. Copy and paste this:
Hi, can you confirm whether our [hosting account / server / device model] is patched for these Linux kernel vulnerabilities: CVE-2026-46300 (Fragnesia), CVE-2026-43284 and CVE-2026-43500 (Dirty Frag), and CVE-2026-31431 (Copy Fail)? If not, when is the fix expected? Thanks.
A good provider answers with a date or a version number. "We take security seriously" is not an answer.
If a server can't be updated yet
Ubuntu's temporary mitigation for both Dirty Frag and Fragnesia blocks three kernel modules (esp4, esp6 and rxrpc) from loading. The exact commands are in Ubuntu's Dirty Frag post.
There's a catch. Blocking esp4 and esp6 breaks IPsec, which Ubuntu notes is common in VPNs like StrongSwan. If that server runs your VPN, the mitigation will take your VPN down. That's a decision for your IT person, not a copy-and-paste job. And once the fixed kernel is installed, Ubuntu says to remove the mitigation.
If you think a server was already compromised
Signs worth taking seriously: new admin or root accounts nobody created, files changed that shouldn't be, unexplained high CPU, or your host suspending your account for abuse.
- Don't just patch and move on. A patch closes the door; it doesn't remove someone already inside.
- Change passwords and SSH keys for every account on that server, from a different, clean computer.
- Ask your host or IT person to check logs and, if there's any doubt, rebuild the server from a known-good backup.
Keeping this from becoming a fire drill
Three serious kernel bugs in about three weeks isn't a fluke. It's the normal pace now. What helps:
- Keep a one-page inventory of everything that runs Linux, who manages it, and where its security updates come from. A spreadsheet with four columns works: device or service, who manages it, how it's updated, last patched.
- Turn on automatic security updates where the system supports it, and schedule reboots. On Ubuntu, the unattended-upgrades tool is installed and turned on for security updates by default, but it doesn't reboot unless you change its Automatic-Reboot setting (Ubuntu Server docs). A kernel fix needs that reboot.
- Limit who can log in. Fewer accounts on a server means fewer footholds for a bug like this. Every account should use MFA or SSH keys, not just a password.
- Subscribe to your vendors' security advisories for the firewall, NAS and VPN. Most have an email list or RSS feed.
- Retire what's no longer getting updates. An old NAS that stopped receiving firmware will never get this fix.
When to get help
- You don't know which of your systems run Linux, or who's responsible for patching them.
- Your website host or appliance vendor can't tell you whether they're patched.
- You've seen any of the compromise signs above.
If you already have an IT person and want someone watching for attacks alongside them, that's what co-managed security is for. Otherwise, get in touch.
Related reading
- Can a stranger reach your office computer? How to lock down remote access
- Your old website could still be leaking information years later
- Hackers are breaking into Windows networks, and it's easier than you think
Originally published May 2026. Updated October 2026.






No comments yet