Linode incident

[Fragnesia] Linux Privilege Escalation Vulnerability

Notice Ongoing View vendor source →

Linode is currently experiencing a notice incident affecting US-East (Newark) and US-East (Newark) Block Storage and 1 more component, which began 57 min ago. The vendor's full update timeline is below.

Started
May 13, 2026, 09:02 PM UTC
Resolved
Ongoing
Duration
● 57m
Detected by Pingoru
May 13, 2026, 09:02 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)US-IAD-2 (Washington 2)

Update timeline

  1. investigating May 13, 2026, 09:02 PM UTC

    Akamai is aware of the recently disclosed “Fragnesia”[1] vulnerability, following the “DirtyFrag”[2] and “CopyFail”[3] disclosures. This vulnerability is very similar in nature and has a similar impact, exploit path, and mitigation approach. We have not observed any related malicious exploits targeting our infrastructure and are continuing to address the vulnerability across our product portfolio and internal systems. As with “CopyFail” and “DirtyFrag”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “Fragnesia” vulnerability was disclosed prior to upstream patches having been made available, we are forced to wait for the different OS providers to create new releases or patches before we can integrate them into the versions we make available to customers. As this is a rapidly developing incident, we will provide further information regarding recommended actions, possible mitigations, and OS updates for all customers who may be affected. [1] https://github.com/v12-security/pocs/tree/main/fragnesia [2] https://github.com/V4bel/dirtyfrag/blob/master/assets/write-up.md [3] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/