Outage in Linode
(Copy Fail) Linux Kernel Local Privilege Escalation Vulnerability [CVE-2026-31431]
Minor
May 01, 2026 - Started 1 day ago
Official incident page
Official incident page
Incident Report
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
Components affected
Linode US-East (Newark) NodeBalancers Linode US-East (Newark) Backups Linode US-East (Newark) Object Storage Linode US-East (Newark) Linode US-East (Newark) Kubernetes Engine Linode US-East (Newark) Block Storage Linode US-Central (Dallas) Kubernetes Engine Linode US-Central (Dallas) Linode US-Central (Dallas) Block Storage Linode EU-Central (Frankfurt) Object Storage Linode US-Central (Dallas) Backups Linode US-Central (Dallas) NodeBalancers Linode AP-South (Singapore) Object Storage Linode US-West (Fremont) Kubernetes Engine Linode US-West (Fremont) Backups Linode US-West (Fremont) Linode US-West (Fremont) Block Storage Linode US-West (Fremont) NodeBalancers Linode US-Southeast (Atlanta) NodeBalancers Linode CA-Central (Toronto) Block Storage Linode US-Southeast (Atlanta) Backups Linode US-Southeast (Atlanta) Linode CA-Central (Toronto) Kubernetes Engine Linode EU-West (London) Block Storage Linode CA-Central (Toronto) Backups Linode EU-West (London) Kubernetes Engine Linode CA-Central (Toronto) NodeBalancers Linode CA-Central (Toronto) Linode EU-Central (Frankfurt) Kubernetes Engine Linode EU-West (London) Linode EU-West (London) Backups Linode EU-West (London) NodeBalancers Linode EU-Central (Frankfurt) Block Storage Linode EU-Central (Frankfurt) Backups Linode EU-Central (Frankfurt) Linode AP-South (Singapore) Kubernetes Engine Linode EU-Central (Frankfurt) NodeBalancers Linode AP-South (Singapore) Block Storage Linode AP-South (Singapore) Linode AP-Northeast-2 (Tokyo 2) Block Storage Linode AP-Northeast-2 (Tokyo 2) Kubernetes Engine Linode AP-South (Singapore) Backups Linode AP-South (Singapore) NodeBalancers Linode AP-West (Mumbai) Block Storage Linode AP-West (Mumbai) Kubernetes Engine Linode AP-Northeast-2 (Tokyo 2) NodeBalancers Linode AP-Northeast-2 (Tokyo 2) Linode AP-Northeast-2 (Tokyo 2) Backups Linode AP-Southeast (Sydney) Kubernetes Engine Linode AP-West (Mumbai) Backups Linode AP-West (Mumbai) NodeBalancers Linode AP-West (Mumbai) Linode AP-Southeast (Sydney) Backups Linode AP-Southeast (Sydney) Linode AP-Southeast (Sydney) NodeBalancersTrusted by 1,000+ teams
Never miss outages in third-party dependencies
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
Latest Updates ( sorted recent to last )
INVESTIGATING
1 day ago - at 05/01/2026 05:52PM
We are continuing to investigate this issue.
INVESTIGATING
1 day ago - at 05/01/2026 05:51PM
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
Latest Linode outages
Object Storage Key creation and validation failing with error 403 in multiple data centers - 3 days ago
Service Issue - Linode Kubernetes Engine (LKE) - 8 days ago
Never miss outages in third-party dependencies
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with
