← Live dashboard

[DirtyFrag] Linux Privilege Escalation Vulnerability

ResolvedminorOfficial source confirmedGlobal service disruptionFirst recorded update May 8, 2026, 01:40 PM · Resolved Jul 6, 2026, 02:41 PM

We have completed our investigation and response to the "DirtyFrag" (CVE-2026-43500, CVE-2026-43284) and "Fragnesia" (CVE-2026-46300) vulnerabilities. We have published documentation articles with detailed guidance on available mitigations and recommended actions for affected systems. Customers can find more information and step-by-step instructions here: https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/ https://www.linode.com/docs/guides/dirty-frag-mitigation/ We encourage all customers to review the article and apply the appropriate mitigations to their...

Linode live status →

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Linode now? Check the current status

Affected services

US-SEA (Seattle)IN-MAA (Chennai) Block StorageIN-BOM-2 (Mumbai 2)JP-OSA (Osaka) BackupsAP-Northeast-2 (Tokyo 2) NodeBalancersAP-West (Mumbai) Linode Kubernetes EngineSE-STO (Stockholm) BackupsAP-Southeast (Sydney) NodeBalancersAU-MEL (Melbourne)EU-Central (Frankfurt) Block StorageJP-TYO-3 (Tokyo 3)ES-MAD (Madrid) BackupsCA-Central (Toronto) NodeBalancersGB-LON (London 2) Block StorageLinode.comLongviewAkamai Cloud Pulse (ACLP) - LogsMX-QRO (Queretaro)US-Central (Dallas) BackupsFR-PAR-2 (Paris 2)IT-MIL (Milan) Linode Kubernetes EngineUS-LAX (Los Angeles) Object StorageFR-MRS (Marseille)US-ORD (Chicago) NodeBalancersBR-GRU (São Paulo) NodeBalancersUS-IAD (Washington) Block StorageDE-FRA-2 (Frankfurt 2)US-IAD (Washington) Linode Kubernetes EngineIT-MIL (Milan) Object StorageGB-LON (London 2) Object StorageUS-MIA (Miami)AP-West (Mumbai) BackupsEU-Central (Frankfurt) Object StorageES-MAD (Madrid) NodeBalancersNL-AMS (Amsterdam) Block StorageAU-MEL (Melbourne) Linode Kubernetes EngineJP-OSA (Osaka) Linode Kubernetes EngineUS-MIA (Miami) NodeBalancersUS-DEN (Denver)ID-CGK (Jakarta) BackupsFR-PAR (Paris)US-East (Newark) Linode Kubernetes EngineUS-East (Newark) BackupsIN-BOM-2 (Mumbai 2) NodeBalancersIN-MAA (Chennai)US-IAD (Washington) NodeBalancersEU-West (London)NL-AMS (Amsterdam) NodeBalancersAP-West (Mumbai) Block StorageUS-SEA (Seattle) Linode Kubernetes EngineUS-Southeast (Atlanta) BackupsUS-LAX (Los Angeles) Block StorageUS-MIA (Miami) Linode Kubernetes EngineNL-AMS (Amsterdam) Linode Kubernetes EngineID-CGK (Jakarta)BR-GRU (São Paulo) Linode Kubernetes EngineUS-IAD (Washington) BackupsUS-Southeast (Atlanta) NodeBalancersSE-STO (Stockholm) Block StorageZA-JNB (Johannesburg)EU-West (London) BackupsUS-Southeast (Atlanta)IT-MIL (Milan) Block StorageIN-BOM-2 (Mumbai 2) BackupsUS-LAX (Los Angeles) NodeBalancersUS-East (Newark) NodeBalancersFR-PAR (Paris) Block StorageSE-STO (Stockholm) Object StorageCA-Central (Toronto) BackupsUS-SEA (Seattle) Object StorageHosted DNS ServiceIN-BOM-2 (Mumbai 2) Linode Kubernetes EngineCL-SCL (Santiago)GB-LON (London 2) NodeBalancersUS-Central (Dallas) Linode Kubernetes EngineBR-GRU (São Paulo) Block StorageSG-SIN-2 (Singapore 2) Linode Kubernetes EngineAP-Northeast-2 (Tokyo 2) Block StorageAP-Southeast (Sydney) Block StorageUS-ORD (Chicago) Linode Kubernetes EngineJP-TYO-3 (Tokyo 3) NodeBalancersDE-HAM (Hamburg)JP-TYO-3 (Tokyo) BackupsEU-Central (Frankfurt) Linode Kubernetes EngineAP-West (Mumbai) NodeBalancersUS-Southeast (Atlanta) Object StorageES-MAD (Madrid)AU-MEL (Melbourne) NodeBalancersFR-PAR (Paris) Object StorageUS-Central (Dallas) Block StorageEU-West (London) NodeBalancersCO-BOG (Bogota)US-ORD (Chicago) BackupsSE-STO (Stockholm) NodeBalancersUS-West (Fremont) BackupsAU-MEL (Melbourne) BackupsAP-Northeast (Tokyo 2) Linode Kubernetes EngineJP-OSA (Osaka)FR-PAR (Paris) BackupsUS-ORD (Chicago)GB-LON (London 2)BR-GRU (São Paulo)AP-Southeast (Sydney) Linode Kubernetes EngineUS-Central (Dallas)US-East (Newark)AP-Northeast-2 (Tokyo 2) BackupsLinode Manager and APIUS-MIA (Miami) Object StorageUS-LAX (Los Angeles)US-West (Fremont)IN-MAA (Chennai) NodeBalancersUS-IAD-2 (Washington 2)CA-Central (Toronto) Block StorageAP-West (Mumbai)US-IAD (Washington) Object StorageES-MAD (Madrid) Linode Kubernetes EngineDE-FRA-2 (Frankfurt 2) BackupsAP-South (Singapore) Object StorageEU-West (London) Block StorageUS-ORD (Chicago) Block StorageJP-OSA (Osaka) Object StorageAP-South (Singapore)JP-TYO-3 (Tokyo 3) Object StorageUS-West (Fremont) Linode Kubernetes EngineES-MAD (Madrid) Block StorageAP-Southeast (Sydney) BackupsDE-FRA-2 (Frankfurt 2) Block StorageNL-AMS (Amsterdam) Object StorageMY-KUL (Kuala Lumpur)US-LAX (Los Angeles) Linode Kubernetes EngineAP-Southeast (Sydney)US-LAX (Los Angeles) BackupsIT-MIL (Milan)ES-MAD (Madrid) Object StorageSG-SIN-2 (Singapore 2)AP-South (Singapore) BackupsIT-MIL (Milan) BackupsManaged DatabasesSG-SIN-2 (Singapore 2) NodeBalancersIN-MAA (Chennai) BackupsUS-SEA (Seattle) Block StorageSG-SIN-2 (Singapore 2) BackupsDE-FRA-2 (Frankfurt 2) Linode Kubernetes EngineUS-East (Newark) Block StorageEU-Central (Frankfurt)CA-Central (Toronto)US-East (Newark) Object StorageEU-West (London) Linode Kubernetes EngineIN-MAA (Chennai) Linode Kubernetes EngineIN-BOM-2 (Mumbai 2) Object StorageID-CGK (Jakarta) Object StorageSG-SIN-2 (Singapore 2) Block StorageJP-OSA (Osaka) NodeBalancersID-CGK (Jakarta) Linode Kubernetes EngineAU-MEL (Melbourne) Object StorageUS-Southeast (Atlanta) Block StorageUS-MIA (Miami) Block StorageNZ-AKL (Auckland)SE-STO (Stockholm) Linode Kubernetes EngineDE-FRA-2 (Frankfurt 2) NodeBalancersUS-Southeast (Atlanta) Linode Kubernetes EngineGB-LON (London 2) Linode Kubernetes EngineUS-West (Fremont) Block StorageUS-SEA (Seattle) NodeBalancersUS-MIA (Miami) BackupsDE-FRA-2 (Frankfurt 2) Object StorageSE-STO (Stockholm)NL-AMS (Amsterdam) BackupsAP-South (Singapore) Linode Kubernetes EngineUS-SEA (Seattle) BackupsIT-MIL (Milan) NodeBalancersAP-South (Singapore) NodeBalancersFR-PAR (Paris) NodeBalancersEU-Central (Frankfurt) BackupsID-CGK (Jakarta) Block StorageCA-Central (Toronto) Linode Kubernetes EngineCloud Manager and APIUS-HOU (Houston)NL-AMS (Amsterdam)US-Central (Dallas) NodeBalancersIN-BOM-2 (Mumbai 2) Block StorageUS-ORD (Chicago) Object StorageGB-LON (London 2) BackupsUS-IAD (Washington)JP-TYO-3 (Tokyo 3) Block StorageJP-TYO-3 (Tokyo 3) Linode Kubernetes EngineAP-South (Singapore) Block StorageBR-GRU (São Paulo) BackupsBR-GRU (Sao Paulo) Object StorageUS-West (Fremont) NodeBalancersID-CGK (Jakarta) NodeBalancersIN-MAA (Chennai) Object StorageAP-Northeast-2 (Tokyo 2)FR-PAR (Paris) Linode Kubernetes EngineSG-SIN-2 (Singapore 2) Object StorageAU-MEL (Melbourne) Block StorageEU-Central (Frankfurt) NodeBalancersJP-OSA (Osaka) Block Storage

Updates (5)

  1. Jul 6, 2026, 02:41 PM
    [DirtyFrag] Linux Privilege Escalation Vulnerability

    We have completed our investigation and response to the "DirtyFrag" (CVE-2026-43500, CVE-2026-43284) and "Fragnesia" (CVE-2026-46300) vulnerabilities. We have published documentation articles with detailed guidance on available mitigations and recommended actions for affected systems. Customers can find more information and step-by-step instructions here: https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/ https://www.linode.com/docs/guides/dirty-frag-mitigation/ We encourage all customers to review the article and apply the appropriate mitigations to their environme

    Linode ↗
  2. Jun 5, 2026, 08:23 PM
    [DirtyFrag] Linux Privilege Escalation Vulnerability

    We are responding to the publication of the most recent variation of the CopyFail[1] adjacent vulnerabilities “DirtyFrag” and “Fragnesia” with additional updates while we wait for upstream OS providers to release patches. Please see our detailed advisory[2] for more information on the current status, possible mitigation mechanisms, and our recommended actions. We will provide another update when more OS images have been updated and/or additional attack vectors are discovered. [1] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/ [2] https://www.linode.com/docs/guides/

    Linode ↗
  3. May 15, 2026, 05:28 PM
    [DirtyFrag] Linux Privilege Escalation Vulnerability

    We are responding to the publication of the most recent variation of the CopyFail[1] adjacent vulnerabilities “DirtyFrag” and “Fragnesia” with additional updates while we wait for upstream OS providers to release patches. Please see our detailed advisory[2] for more information on the current status, possible mitigation mechanisms, and our recommended actions. We will provide another update when more OS images have been updated and/or additional attack vectors are discovered. [1] https://www.linode.com/docs/guides/cve-2026-31431-copy-fail-mitigation/ [2] https://www.linode.com/docs/guides/

    Linode ↗
  4. May 9, 2026, 02:40 PM
    [DirtyFrag] Linux Privilege Escalation Vulnerability

    We have updated our latest Linode kernel to version 7.0.5, which contains the upstream fix from kernel.org for the DirtyFrag vulnerabilities as well as the previous fixes for the recent CopyFail vulnerability. This kernel is available in Cloud Manager and we recommend customers using the Linode-compiled kernel update their configurations to this kernel. We are in parallel tracking the upstream Linux distributions and will provide another update when fixed versions have been released.

    Linode ↗
  5. May 8, 2026, 01:40 PM
    [DirtyFrag] Linux Privilege Escalation Vulnerability

    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 hav

    Linode ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow Linode's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.