Live / Linode / Incident
Linode: Customer Security Advisory: CVE-2026-98432
Linode · linode.comResolved2026-11-09 21:23 UTC
Public — what happened
Summary
Linode, through its parent Akamai, said on 2026-10-30 that it was aware of a publicly disclosed security flaw, CVE-2026-98432, that could allow remote code execution, and that it was investigating and taking protective steps. Within a day it said it was deploying mitigations and had no evidence the flaw had been exploited on its compute platform, while advising customers to install operating system updates from their own providers once available. By 2026-11-02 it said it was rolling out kernel patches and had added network rules that drop certain IPv4 packets, which it said removes the immediate remote attack route without hurting performance. The incident is marked resolved as of 2026-11-09.
Timeline
- Started — 2026-10-30 18:10 UTC
- Investigating — 2026-10-30 18:10 UTC (4 updates)
- Resolved — 2026-11-09 21:23 UTC · 10 days after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Linode against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Linode: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Linode report →
More from Linode
Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.