Linode incident

(Copy Fail) Linux Kernel Local Privilege Escalation Vulnerability [CVE-2026-31431]

Started
May 01, 2026, 05:51 PM UTC
Resolved
Ongoing
Duration
● 2d 5h
Detected by Pingoru
May 01, 2026, 05:51 PM UTC

Affected components

US-East (Newark)US-East (Newark) Block StorageUS-East (Newark) NodeBalancersUS-East (Newark) BackupsUS-East (Newark) Object StorageUS-East (Newark) Linode Kubernetes EngineUS-Central (Dallas)US-Central (Dallas) Block StorageUS-Central (Dallas) NodeBalancersUS-Central (Dallas) BackupsUS-Central (Dallas) Linode Kubernetes EngineUS-Southeast (Atlanta) Object StorageUS-West (Fremont)US-West (Fremont) Block StorageUS-West (Fremont) NodeBalancersUS-West (Fremont) BackupsUS-West (Fremont) Linode Kubernetes EngineUS-IAD (Washington) Object StorageUS-Southeast (Atlanta)US-Southeast (Atlanta) NodeBalancersUS-Southeast (Atlanta) BackupsUS-Southeast (Atlanta) Block StorageUS-Southeast (Atlanta) Linode Kubernetes EngineUS-ORD (Chicago) Object StorageEU-Central (Frankfurt) Object StorageUS-IAD (Washington)US-IAD (Washington) BackupsUS-IAD (Washington) Block StorageUS-IAD (Washington) NodeBalancersUS-IAD (Washington) Linode Kubernetes EngineAP-South (Singapore) Object StorageUS-ORD (Chicago)US-ORD (Chicago) BackupsUS-ORD (Chicago) Block StorageUS-ORD (Chicago) NodeBalancersUS-ORD (Chicago) Linode Kubernetes EngineCA-Central (Toronto)CA-Central (Toronto) Block StorageCA-Central (Toronto) NodeBalancersCA-Central (Toronto) BackupsCA-Central (Toronto) Linode Kubernetes EngineFR-PAR (Paris) Object StorageEU-West (London)EU-West (London) Block StorageEU-West (London) NodeBalancersEU-West (London) BackupsEU-West (London) Linode Kubernetes EngineSE-STO (Stockholm) Object StorageEU-Central (Frankfurt)EU-Central (Frankfurt) Block StorageEU-Central (Frankfurt) NodeBalancersEU-Central (Frankfurt) BackupsEU-Central (Frankfurt) Linode Kubernetes EngineUS-SEA (Seattle) Object StorageFR-PAR (Paris)FR-PAR (Paris) BackupsFR-PAR (Paris) Block StorageFR-PAR (Paris) NodeBalancersFR-PAR (Paris) Linode Kubernetes EngineJP-OSA (Osaka) Object StorageAP-South (Singapore)AP-South (Singapore) Block StorageAP-South (Singapore) NodeBalancersAP-South (Singapore) BackupsAP-South (Singapore) Linode Kubernetes EngineIN-MAA (Chennai) Object StorageAP-Northeast-2 (Tokyo 2)AP-Northeast-2 (Tokyo 2) NodeBalancersAP-Northeast-2 (Tokyo 2) BackupsAP-Northeast-2 (Tokyo 2) Block StorageAP-Northeast (Tokyo 2) Linode Kubernetes EngineID-CGK (Jakarta) Object StorageAP-West (Mumbai)AP-West (Mumbai) Block StorageAP-West (Mumbai) NodeBalancersAP-West (Mumbai) BackupsAP-West (Mumbai) Linode Kubernetes EngineBR-GRU (Sao Paulo) Object StorageAP-Southeast (Sydney)AP-Southeast (Sydney) NodeBalancersAP-Southeast (Sydney) BackupsAP-Southeast (Sydney) Linode Kubernetes EngineAP-Southeast (Sydney) Block StorageES-MAD (Madrid) Object StorageSE-STO (Stockholm)SE-STO (Stockholm) BackupsSE-STO (Stockholm) Block StorageSE-STO (Stockholm) NodeBalancersSE-STO (Stockholm) Linode Kubernetes EngineUS-SEA (Seattle)US-SEA (Seattle) BackupsUS-SEA (Seattle) Block StorageUS-SEA (Seattle) NodeBalancersUS-SEA (Seattle) Linode Kubernetes EngineIT-MIL (Milan)JP-OSA (Osaka) BackupsJP-OSA (Osaka) Block StorageJP-OSA (Osaka) NodeBalancersJP-OSA (Osaka) Linode Kubernetes EngineGB-LON (London 2)JP-OSA (Osaka)IN-MAA (Chennai) BackupsIN-MAA (Chennai) Block StorageIN-MAA (Chennai) NodeBalancersIN-MAA (Chennai) Linode Kubernetes EngineAU-MEL (Melbourne)IN-MAA (Chennai)ID-CGK (Jakarta) Linode Kubernetes EngineBR-GRU (São Paulo) BackupsBR-GRU (São Paulo) Block StorageBR-GRU (São Paulo) NodeBalancersNL-AMS (Amsterdam) Object StorageID-CGK (Jakarta)NL-AMS (Amsterdam) BackupsNL-AMS (Amsterdam) Block StorageNL-AMS (Amsterdam) NodeBalancersIT-MIL (Milan) Object StorageBR-GRU (São Paulo) Linode Kubernetes EngineBR-GRU (São Paulo)ES-MAD (Madrid) BackupsES-MAD (Madrid) Block StorageES-MAD (Madrid) NodeBalancersUS-MIA (Miami) Object StorageNL-AMS (Amsterdam) Linode Kubernetes EngineNL-AMS (Amsterdam)IT-MIL (Milan) BackupsIT-MIL (Milan) Block StorageIT-MIL (Milan) NodeBalancersUS-LAX (Los Angeles) Object StorageES-MAD (Madrid) Linode Kubernetes EngineUS-MIA (Miami)US-MIA (Miami) BackupsUS-MIA (Miami) Block StorageUS-MIA (Miami) NodeBalancersGB-LON (London 2) Object StorageIT-MIL (Milan) Linode Kubernetes EngineUS-LAX (Los Angeles)ID-CGK (Jakarta) BackupsID-CGK (Jakarta) Block StorageID-CGK (Jakarta) NodeBalancersAU-MEL (Melbourne) Object StorageUS-MIA (Miami) Linode Kubernetes EngineES-MAD (Madrid)US-LAX (Los Angeles) BackupsUS-LAX (Los Angeles) Block StorageUS-LAX (Los Angeles) NodeBalancersIN-BOM-2 (Mumbai 2) Object StorageUS-LAX (Los Angeles) Linode Kubernetes EngineAU-MEL (Melbourne)GB-LON (London 2) BackupsGB-LON (London 2) Block StorageGB-LON (London 2) NodeBalancersDE-FRA-2 (Frankfurt 2) Object StorageGB-LON (London 2) Linode Kubernetes EngineGB-LON (London 2)AU-MEL (Melbourne) BackupsAU-MEL (Melbourne) Block StorageAU-MEL (Melbourne) NodeBalancersSG-SIN-2 (Singapore 2) Object StorageAU-MEL (Melbourne) Linode Kubernetes EngineIN-BOM-2 (Mumbai 2)IN-BOM-2 (Mumbai 2) BackupsIN-BOM-2 (Mumbai 2) Block StorageIN-BOM-2 (Mumbai 2) NodeBalancersJP-TYO-3 (Tokyo 3) Object StorageIN-BOM-2 (Mumbai 2) Linode Kubernetes EngineSG-SIN-2 (Singapore 2)DE-FRA-2 (Frankfurt 2) BackupsDE-FRA-2 (Frankfurt 2) Block StorageDE-FRA-2 (Frankfurt 2) NodeBalancersDE-FRA-2 (Frankfurt 2) Linode Kubernetes EngineDE-FRA-2 (Frankfurt 2)SG-SIN-2 (Singapore 2) BackupsSG-SIN-2 (Singapore 2) Block StorageSG-SIN-2 (Singapore 2) NodeBalancersSG-SIN-2 (Singapore 2) Linode Kubernetes EngineJP-TYO-3 (Tokyo 3)JP-TYO-3 (Tokyo) BackupsJP-TYO-3 (Tokyo 3) Block StorageJP-TYO-3 (Tokyo 3) NodeBalancersJP-TYO-3 (Tokyo 3) Linode Kubernetes EngineZA-JNB (Johannesburg)NZ-AKL (Auckland)CO-BOG (Bogota)US-DEN (Denver)DE-HAM (Hamburg)US-HOU (Houston)MY-KUL (Kuala Lumpur)FR-MRS (Marseille)MX-QRO (Queretaro)CL-SCL (Santiago)FR-PAR-2 (Paris 2)

Update timeline

  1. investigating May 01, 2026, 05:51 PM UTC

    Akamai is aware of the recently disclosed “Copy Fail” vulnerability (CVE-2026-31431). We are assessing the issue and are working to address it across our product portfolio and internal systems. While we have not observed any related malicious exploits targeting our infrastructure, Akamai continuously works to reduce risks and enhance our security posture. We are taking both immediate and longer-term steps to mitigate potential impacts and help ensure the continued confidence of our customers. Per our Shared Security Model[1], customers are responsible for making sure their service’s installed applications and code are securely configured and patched. Given the nature of this vulnerability, it should be assumed that all virtual machines running Linux are at-risk until patched. We will be publishing more details as patches are incorporated into the base images that we supply, but we strongly recommend customers deploy mitigations on all instances. Furthermore, the nature of the vulnerability suggests that container escapes are possible, so customers allowing untrusted workloads to execute in their containers may need to take additional steps to secure their containerized workloads. We will provide further information regarding our posture and recommended actions for Akamai Compute customers who may be affected. [1] https://www.akamai.com/legal/security

  2. investigating May 01, 2026, 05:52 PM UTC

    We are continuing to investigate this issue.

Looking to track Linode downtime and outages?

Pingoru polls Linode's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Linode reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Linode alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Linode for free

5 free monitors · No credit card required