Linode incident
[DirtyFrag] Linux Privilege Escalation Vulnerability
Linode is currently experiencing a notice incident affecting US-East (Newark) and Linode.com and 1 more component, which began 14h ago. The vendor's full update timeline is below.
Affected components
US-East (Newark)Linode.comUS-East (Newark) Block StorageUS-East (Newark) NodeBalancersUS-East (Newark) BackupsUS-East (Newark) Object StorageUS-East (Newark) Linode Kubernetes EngineUS-East (Newark)Linode Manager and APIUS-Central (Dallas)US-Central (Dallas) Block StorageUS-Central (Dallas) NodeBalancersUS-Central (Dallas) BackupsUS-Central (Dallas) Linode Kubernetes EngineUS-Southeast (Atlanta) Object StorageUS-Central (Dallas)US-West (Fremont)Hosted DNS ServiceUS-West (Fremont) Block StorageUS-West (Fremont) NodeBalancersUS-West (Fremont) BackupsUS-West (Fremont) Linode Kubernetes EngineUS-IAD (Washington) Object StorageUS-West (Fremont)US-Southeast (Atlanta)US-Southeast (Atlanta) NodeBalancersUS-Southeast (Atlanta) BackupsLongviewUS-Southeast (Atlanta) Block StorageUS-Southeast (Atlanta) Linode Kubernetes EngineUS-ORD (Chicago) Object StorageUS-Southeast (Atlanta)EU-Central (Frankfurt) Object StorageManaged DatabasesUS-IAD (Washington)US-IAD (Washington) BackupsUS-IAD (Washington) Block StorageUS-IAD (Washington) NodeBalancersUS-IAD (Washington) Linode Kubernetes EngineUS-IAD (Washington)AP-South (Singapore) Object StorageUS-ORD (Chicago)US-ORD (Chicago) BackupsUS-ORD (Chicago) Block StorageUS-ORD (Chicago) NodeBalancersUS-ORD (Chicago) Linode Kubernetes EngineUS-ORD (Chicago)ACLP LogsCA-Central (Toronto)CA-Central (Toronto) Block StorageCA-Central (Toronto) NodeBalancersCA-Central (Toronto) BackupsCA-Central (Toronto) Linode Kubernetes EngineFR-PAR (Paris) Object StorageCA-Central (Toronto)EU-West (London)EU-West (London) Block StorageEU-West (London) NodeBalancersEU-West (London) BackupsEU-West (London) Linode Kubernetes EngineSE-STO (Stockholm) Object StorageEU-West (London)EU-Central (Frankfurt)EU-Central (Frankfurt) Block StorageEU-Central (Frankfurt) NodeBalancersEU-Central (Frankfurt) BackupsEU-Central (Frankfurt) Linode Kubernetes EngineUS-SEA (Seattle) Object StorageEU-Central (Frankfurt)FR-PAR (Paris)FR-PAR (Paris) BackupsFR-PAR (Paris) Block StorageFR-PAR (Paris) NodeBalancersFR-PAR (Paris) Linode Kubernetes EngineJP-OSA (Osaka) Object StorageFR-PAR (Paris)AP-South (Singapore)AP-South (Singapore) Block StorageAP-South (Singapore) NodeBalancersAP-South (Singapore) BackupsAP-South (Singapore) Linode Kubernetes EngineIN-MAA (Chennai) Object StorageAP-South (Singapore)AP-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-Northeast-2 (Tokyo 2)AP-West (Mumbai)AP-West (Mumbai) Block StorageAP-West (Mumbai) NodeBalancersAP-West (Mumbai) BackupsAP-West (Mumbai) Linode Kubernetes EngineBR-GRU (Sao Paulo) Object StorageAP-West (Mumbai)AP-Southeast (Sydney)AP-Southeast (Sydney) NodeBalancersAP-Southeast (Sydney) BackupsAP-Southeast (Sydney) Linode Kubernetes EngineAP-Southeast (Sydney) Block StorageES-MAD (Madrid) Object StorageAP-Southeast (Sydney)SE-STO (Stockholm)SE-STO (Stockholm) BackupsSE-STO (Stockholm) Block StorageSE-STO (Stockholm) NodeBalancersSE-STO (Stockholm) Linode Kubernetes EngineSE-STO (Stockholm)US-SEA (Seattle)US-SEA (Seattle) BackupsUS-SEA (Seattle) Block StorageUS-SEA (Seattle) NodeBalancersUS-SEA (Seattle) Linode Kubernetes EngineUS-SEA (Seattle)IT-MIL (Milan)JP-OSA (Osaka) BackupsJP-OSA (Osaka) Block StorageJP-OSA (Osaka) NodeBalancersJP-OSA (Osaka) Linode Kubernetes EngineGB-LON (London 2)IT-MIL (Milan)JP-OSA (Osaka)IN-MAA (Chennai) BackupsIN-MAA (Chennai) Block StorageIN-MAA (Chennai) NodeBalancersIN-MAA (Chennai) Linode Kubernetes EngineAU-MEL (Melbourne)JP-OSA (Osaka)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 StorageIN-MAA (Chennai)ID-CGK (Jakarta)NL-AMS (Amsterdam) BackupsNL-AMS (Amsterdam) Block StorageNL-AMS (Amsterdam) NodeBalancersIT-MIL (Milan) Object StorageBR-GRU (São Paulo) Linode Kubernetes EngineID-CGK (Jakarta)BR-GRU (São Paulo)ES-MAD (Madrid) BackupsES-MAD (Madrid) Block StorageES-MAD (Madrid) NodeBalancersUS-MIA (Miami) Object StorageNL-AMS (Amsterdam) Linode Kubernetes EngineBR-GRU (São Paulo)NL-AMS (Amsterdam)IT-MIL (Milan) BackupsIT-MIL (Milan) Block StorageIT-MIL (Milan) NodeBalancersUS-LAX (Los Angeles) Object StorageES-MAD (Madrid) Linode Kubernetes EngineNL-AMS (Amsterdam)US-MIA (Miami)US-MIA (Miami) BackupsUS-MIA (Miami) Block StorageUS-MIA (Miami) NodeBalancersGB-LON (London 2) Object StorageIT-MIL (Milan) Linode Kubernetes EngineUS-MIA (Miami)US-LAX (Los Angeles)ID-CGK (Jakarta) BackupsID-CGK (Jakarta) Block StorageID-CGK (Jakarta) NodeBalancersAU-MEL (Melbourne) Object StorageUS-MIA (Miami) Linode Kubernetes EngineUS-LAX (Los Angeles)ES-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 EngineES-MAD (Madrid)AU-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 EngineAU-MEL (Melbourne)GB-LON (London 2)AU-MEL (Melbourne) BackupsAU-MEL (Melbourne) Block StorageAU-MEL (Melbourne) NodeBalancersSG-SIN-2 (Singapore 2) Object StorageAU-MEL (Melbourne) Linode Kubernetes EngineGB-LON (London 2)IN-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 EngineIN-BOM-2 (Mumbai 2)SG-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 EngineSG-SIN-2 (Singapore 2)DE-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 EngineDE-FRA-2 (Frankfurt 2)JP-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 EngineJP-TYO-3 (Tokyo 3)ZA-JNB (Johannesburg)ZA-JNB (Johannesburg)NZ-AKL (Auckland)NZ-AKL (Auckland)CO-BOG (Bogota)CO-BOG (Bogota)US-DEN (Denver)US-DEN (Denver)DE-HAM (Hamburg)DE-HAM (Hamburg)US-HOU (Houston)US-HOU (Houston)MY-KUL (Kuala Lumpur)MY-KUL (Kuala Lumpur)FR-MRS (Marseille)FR-MRS (Marseille)MX-QRO (Queretaro)MX-QRO (Queretaro)CL-SCL (Santiago)CL-SCL (Santiago)FR-PAR-2 (Paris 2)US-IAD-2 (Washington 2)
Update timeline
- investigating May 08, 2026, 01:40 PM UTC
Akamai is aware of the recently disclosed “DirtyFrag”[1] vulnerability that followed the “CopyFail”[2] disclosure. 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”, we are advising customers to consider most Linux distributions to be at-risk until patched. Since the “DirtyFrag” 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/V4bel/dirtyfrag/blob/master/assets/write-up.md [2] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/