Home › Service directory › Linode › Outage History ›
[Fragnesia] Linux Privilege Escalation Vulnerability Linode incident
[Fragnesia] Linux Privilege Escalation Vulnerability 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.
Affected components US-East (Newark) US-East (Newark) Block Storage US-East (Newark) NodeBalancers US-East (Newark) Backups US-East (Newark) Object Storage US-East (Newark) Linode Kubernetes Engine US-Central (Dallas) US-Central (Dallas) Block Storage US-Central (Dallas) NodeBalancers US-Central (Dallas) Backups US-Central (Dallas) Linode Kubernetes Engine US-Southeast (Atlanta) Object Storage US-West (Fremont) US-West (Fremont) Block Storage US-West (Fremont) NodeBalancers US-West (Fremont) Backups US-West (Fremont) Linode Kubernetes Engine US-IAD (Washington) Object Storage US-Southeast (Atlanta) US-Southeast (Atlanta) NodeBalancers US-Southeast (Atlanta) Backups US-Southeast (Atlanta) Block Storage US-Southeast (Atlanta) Linode Kubernetes Engine US-ORD (Chicago) Object Storage EU-Central (Frankfurt) Object Storage US-IAD (Washington) US-IAD (Washington) Backups US-IAD (Washington) Block Storage US-IAD (Washington) NodeBalancers US-IAD (Washington) Linode Kubernetes Engine AP-South (Singapore) Object Storage US-ORD (Chicago) US-ORD (Chicago) Backups US-ORD (Chicago) Block Storage US-ORD (Chicago) NodeBalancers US-ORD (Chicago) Linode Kubernetes Engine CA-Central (Toronto) CA-Central (Toronto) Block Storage CA-Central (Toronto) NodeBalancers CA-Central (Toronto) Backups CA-Central (Toronto) Linode Kubernetes Engine FR-PAR (Paris) Object Storage EU-West (London) EU-West (London) Block Storage EU-West (London) NodeBalancers EU-West (London) Backups EU-West (London) Linode Kubernetes Engine SE-STO (Stockholm) Object Storage EU-Central (Frankfurt) EU-Central (Frankfurt) Block Storage EU-Central (Frankfurt) NodeBalancers EU-Central (Frankfurt) Backups EU-Central (Frankfurt) Linode Kubernetes Engine US-SEA (Seattle) Object Storage FR-PAR (Paris) FR-PAR (Paris) Backups FR-PAR (Paris) Block Storage FR-PAR (Paris) NodeBalancers FR-PAR (Paris) Linode Kubernetes Engine JP-OSA (Osaka) Object Storage AP-South (Singapore) AP-South (Singapore) Block Storage AP-South (Singapore) NodeBalancers AP-South (Singapore) Backups AP-South (Singapore) Linode Kubernetes Engine IN-MAA (Chennai) Object Storage AP-Northeast-2 (Tokyo 2) AP-Northeast-2 (Tokyo 2) NodeBalancers AP-Northeast-2 (Tokyo 2) Backups AP-Northeast-2 (Tokyo 2) Block Storage AP-Northeast (Tokyo 2) Linode Kubernetes Engine ID-CGK (Jakarta) Object Storage AP-West (Mumbai) AP-West (Mumbai) Block Storage AP-West (Mumbai) NodeBalancers AP-West (Mumbai) Backups AP-West (Mumbai) Linode Kubernetes Engine BR-GRU (Sao Paulo) Object Storage AP-Southeast (Sydney) AP-Southeast (Sydney) NodeBalancers AP-Southeast (Sydney) Backups AP-Southeast (Sydney) Linode Kubernetes Engine AP-Southeast (Sydney) Block Storage ES-MAD (Madrid) Object Storage SE-STO (Stockholm) SE-STO (Stockholm) Backups SE-STO (Stockholm) Block Storage SE-STO (Stockholm) NodeBalancers SE-STO (Stockholm) Linode Kubernetes Engine US-SEA (Seattle) US-SEA (Seattle) Backups US-SEA (Seattle) Block Storage US-SEA (Seattle) NodeBalancers US-SEA (Seattle) Linode Kubernetes Engine IT-MIL (Milan) JP-OSA (Osaka) Backups JP-OSA (Osaka) Block Storage JP-OSA (Osaka) NodeBalancers JP-OSA (Osaka) Linode Kubernetes Engine GB-LON (London 2) JP-OSA (Osaka) IN-MAA (Chennai) Backups IN-MAA (Chennai) Block Storage IN-MAA (Chennai) NodeBalancers IN-MAA (Chennai) Linode Kubernetes Engine AU-MEL (Melbourne) IN-MAA (Chennai) ID-CGK (Jakarta) Linode Kubernetes Engine BR-GRU (São Paulo) Backups BR-GRU (São Paulo) Block Storage BR-GRU (São Paulo) NodeBalancers NL-AMS (Amsterdam) Object Storage ID-CGK (Jakarta) NL-AMS (Amsterdam) Backups NL-AMS (Amsterdam) Block Storage NL-AMS (Amsterdam) NodeBalancers IT-MIL (Milan) Object Storage BR-GRU (São Paulo) Linode Kubernetes Engine BR-GRU (São Paulo) ES-MAD (Madrid) Backups ES-MAD (Madrid) Block Storage ES-MAD (Madrid) NodeBalancers US-MIA (Miami) Object Storage NL-AMS (Amsterdam) Linode Kubernetes Engine NL-AMS (Amsterdam) IT-MIL (Milan) Backups IT-MIL (Milan) Block Storage IT-MIL (Milan) NodeBalancers US-LAX (Los Angeles) Object Storage ES-MAD (Madrid) Linode Kubernetes Engine US-MIA (Miami) US-MIA (Miami) Backups US-MIA (Miami) Block Storage US-MIA (Miami) NodeBalancers GB-LON (London 2) Object Storage IT-MIL (Milan) Linode Kubernetes Engine US-LAX (Los Angeles) ID-CGK (Jakarta) Backups ID-CGK (Jakarta) Block Storage ID-CGK (Jakarta) NodeBalancers AU-MEL (Melbourne) Object Storage US-MIA (Miami) Linode Kubernetes Engine ES-MAD (Madrid) US-LAX (Los Angeles) Backups US-LAX (Los Angeles) Block Storage US-LAX (Los Angeles) NodeBalancers IN-BOM-2 (Mumbai 2) Object Storage US-LAX (Los Angeles) Linode Kubernetes Engine AU-MEL (Melbourne) GB-LON (London 2) Backups GB-LON (London 2) Block Storage GB-LON (London 2) NodeBalancers DE-FRA-2 (Frankfurt 2) Object Storage GB-LON (London 2) Linode Kubernetes Engine GB-LON (London 2) AU-MEL (Melbourne) Backups AU-MEL (Melbourne) Block Storage AU-MEL (Melbourne) NodeBalancers SG-SIN-2 (Singapore 2) Object Storage AU-MEL (Melbourne) Linode Kubernetes Engine IN-BOM-2 (Mumbai 2) IN-BOM-2 (Mumbai 2) Backups IN-BOM-2 (Mumbai 2) Block Storage IN-BOM-2 (Mumbai 2) NodeBalancers JP-TYO-3 (Tokyo 3) Object Storage IN-BOM-2 (Mumbai 2) Linode Kubernetes Engine SG-SIN-2 (Singapore 2) DE-FRA-2 (Frankfurt 2) Backups DE-FRA-2 (Frankfurt 2) Block Storage DE-FRA-2 (Frankfurt 2) NodeBalancers DE-FRA-2 (Frankfurt 2) Linode Kubernetes Engine DE-FRA-2 (Frankfurt 2) SG-SIN-2 (Singapore 2) Backups SG-SIN-2 (Singapore 2) Block Storage SG-SIN-2 (Singapore 2) NodeBalancers SG-SIN-2 (Singapore 2) Linode Kubernetes Engine JP-TYO-3 (Tokyo 3) JP-TYO-3 (Tokyo) Backups JP-TYO-3 (Tokyo 3) Block Storage JP-TYO-3 (Tokyo 3) NodeBalancers JP-TYO-3 (Tokyo 3) Linode Kubernetes Engine ZA-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 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/
Other recent Linode outages