← Voltar ao feed

OT fundamentals gap: Google London PLC fault outage, AI-built Linux MPTCP root exploit (CVE-2026-98432), Capcom and DHS identity leaks

1 fonte(s) · 1 atualização(ões) · publicado 17/11/2026 07:42 · coletado há 7 horas

An opinion/podcast-recap article from industrialcyber.co links three stories to weak OT security fundamentals. The first is Google's final report on the europe-west2-b London zone outage. The cause was generator-start PLC logic whose undervoltage sensing was wired on the line side of an isolated utility breaker, so the generators never started. Customer impact lasted 6h08m, and the outage was not an attack. The second is Anthropic's Frontier Red Team report that an unreleased research model wrote a Linux kernel exploit for CVE-2026-98432, a race condition leading to use-after-free in the networking stack. The third is two identity leaks: Capcom (CAPCOM ID, 11,774,247 records) and DHS (more than 41,000 employees and contractors, released by Distributed Denial of Secrets). This record rests on the article alone. No web research was performed, so vendor advisories and CVSS vectors were not checked.

Entenda a falha

A vulnerabilidade

CVE-2026-98432 is a race condition that leads to a use-after-free in the Linux kernel networking stack, reached through Multipath TCP (MPTCP). An attacker needs network reach to a server with an MPTCP listener, and no credentials or user interaction. The result is unauthenticated remote root command execution. The Linux kernel CVE team scored it 9.8, while The Hacker News reported Red Hat, SUSE and Oracle rate it lower. Debian shipped fixes on October 16 and 17. Ubuntu has fixed kernels for 22.04, 24.04 and 26.04 LTS, while 20.04 was still vulnerable as of November 14. The article does not list affected upstream kernel versions.

Como funciona

Network traffic arrives at a server that has an MPTCP listener open, and the kernel's networking stack handles the MPTCP connection state. Two operations on the same kernel object race each other. One of them can free the object while the other still uses it, so the kernel touches memory after it was freed. According to Anthropic's report, this was enough to leak a kernel pointer, defeat KASLR, and then run commands as root. The article gives no finer detail on the exact code path.

Por que é vulnerável

The root cause is a race condition in kernel networking code that ends in a use-after-free: memory is used after it was freed because concurrent operations are not properly synchronized. The article does not say why it went unnoticed or what exactly the fix changes. Exposure depends on MPTCP being reachable, so whether a device is exposed matters as much as its patch status.

Como foi descoberta

On October 27, Anthropic's Frontier Red Team reported that an unreleased internal research model, after initial prompting, wrote an exploit for the bug. The article does not say who first found the flaw or how it was reported. Debian had already shipped fixes on October 16 and 17, so the bug was public before the report. As of late October there was no reported exploitation in the wild and no CISA KEV listing.

PoC existente, privada

O exploit existe, mas quem o tem não o publicou.

Anthropic says its model wrote a working exploit. Against a server with an MPTCP listener, it leaked a kernel pointer to defeat KASLR in 48 minutes and reached root about five minutes later, roughly 53 minutes after the initial prompt. Anthropic did not publish the exploit code, the kernel version or the test configuration, so it is not public. Even so, it shows the path from a disclosed kernel bug to remote root can be short, so patch Linux hosts and devices that expose MPTCP quickly.

Explicação gerada por IA a partir da matéria e dos artigos, em 17/11/2026 09:18.

Detalhes técnicos

  • Google outage: Utility feed B was locked out after an October 14 generator load test. When a cable fault took out feed A, the primary and backup PLCs still read live voltage upstream of the isolated breaker. The UPS batteries (five minutes of runtime) drained. About 40 services were affected, and the wider region degraded through cross-zone control-plane timeouts.
  • CVE-2026-98432: The exploit needs a reachable MPTCP listener. It leaked a kernel pointer to defeat KASLR in 48 minutes, then reached root about five minutes later, with no credentials or user interaction. The Linux kernel CVE team scored it 9.8. Red Hat, SUSE and Oracle reportedly rate it lower. Debian fixed it on October 16 and 17. Ubuntu has fixed kernels for 22.04, 24.04 and 26.04, while 20.04 was still vulnerable as of November 14. As of late October there was no reported exploitation in the wild and no CISA KEV listing.
  • Capcom: Exposed data was email addresses and account metadata (creation date, last login, login count, last-login IP). 196 accounts had passwords changed without authorization. The intrusion method was not disclosed.
  • DHS: The data includes names, emails, phone numbers, job titles and office locations. It is attributed to the hacktivist group "Department of Peace". DDoSecrets claims the data was harvested via Okta SSO. Reuters could not corroborate this, and Okta said it had no evidence of a compromise.

Remediação

  • Google committed to PLC code reviews with vendors, validation of PLC configurations at similar sites (by November 15), generator load transfer tests (by November 17), and PLC code validation at commissioning (by December 18).
  • Inventory Linux-based industrial assets, check which ones expose MPTCP, and track vendor kernel fixes.
  • Enforce MFA on every remote access path into OT.
  • Change reused passwords everywhere they were used.

Linha do tempo

  1. industrialcyber.co ↗ · pub. 17/11/2026 07:42 · coletado 17/11 09:02 primeiro registro

    OT fundamentals gap: Google London PLC fault outage, AI-built Linux MPTCP root exploit (CVE-2026-98432), Capcom and DHS identity leaks

    ler a análise desta fonte

    An opinion/podcast-recap article from industrialcyber.co links three stories to weak OT security fundamentals. The first is Google's final report on the europe-west2-b London zone outage. The cause was generator-start PLC logic whose undervoltage sensing was wired on the line side of an isolated utility breaker, so the generators never started. Customer impact lasted 6h08m, and the outage was not an attack. The second is Anthropic's Frontier Red Team report that an unreleased research model wrote a Linux kernel exploit for CVE-2026-98432, a race condition leading to use-after-free in the networking stack. The third is two identity leaks: Capcom (CAPCOM ID, 11,774,247 records) and DHS (more than 41,000 employees and contractors, released by Distributed Denial of Secrets). This record rests on the article alone. No web research was performed, so vendor advisories and CVSS vectors were not checked.

    Technical Details

    • Google outage: Utility feed B was locked out after an October 14 generator load test. When a cable fault took out feed A, the primary and backup PLCs still read live voltage upstream of the isolated breaker. The UPS batteries (five minutes of runtime) drained. About 40 services were affected, and the wider region degraded through cross-zone control-plane timeouts.
    • CVE-2026-98432: The exploit needs a reachable MPTCP listener. It leaked a kernel pointer to defeat KASLR in 48 minutes, then reached root about five minutes later, with no credentials or user interaction. The Linux kernel CVE team scored it 9.8. Red Hat, SUSE and Oracle reportedly rate it lower. Debian fixed it on October 16 and 17. Ubuntu has fixed kernels for 22.04, 24.04 and 26.04, while 20.04 was still vulnerable as of November 14. As of late October there was no reported exploitation in the wild and no CISA KEV listing.
    • Capcom: Exposed data was email addresses and account metadata (creation date, last login, login count, last-login IP). 196 accounts had passwords changed without authorization. The intrusion method was not disclosed.
    • DHS: The data includes names, emails, phone numbers, job titles and office locations. It is attributed to the hacktivist group "Department of Peace". DDoSecrets claims the data was harvested via Okta SSO. Reuters could not corroborate this, and Okta said it had no evidence of a compromise.

    Remediation

    • Google committed to PLC code reviews with vendors, validation of PLC configurations at similar sites (by November 15), generator load transfer tests (by November 17), and PLC code validation at commissioning (by December 18).
    • Inventory Linux-based industrial assets, check which ones expose MPTCP, and track vendor kernel fixes.
    • Enforce MFA on every remote access path into OT.
    • Change reused passwords everywhere they were used.