Anthropic Researchers Demonstrate Exploit for Linux MPTCP Root Access

En bref

• Anthropic researchers built a functioning exploit for a Linux MPTCP weakness.
• The attack requires no credentials and can yield root-level command execution.
• Exposure is limited to systems operating as MPTCP servers.
• No CVE identifier exists yet; severity is assessed as medium.

Researchers at Anthropic have produced a working attack against a weakness in Linux's Multipath TCP support. The exploit lets an unauthenticated remote party run arbitrary commands with root privileges on affected systems. No CVE identifier has been issued for the issue.

The exposure is narrower than a generic Linux kernel bug: only deployments that actively provide MPTCP services are in scope. Education and government networks should inventory Linux hosts to determine whether MPTCP is enabled, listening, or required for business operations. Systems that do not use MPTCP should not be left exposed by default.

Remote, unauthenticated root access is a serious outcome, but the medium severity rating reflects the constrained attack surface rather than a lack of impact. The absence of a CVE does not mean there is no risk; it means tracking, vendor coordination, and patch communication may lag behind the public discussion of the exploit.

Administrators should treat MPTCP endpoints as sensitive until vendor guidance and kernel updates are available. Watch for unusual inbound connections to MPTCP services, unexpected root-level process activity, and changes to kernel modules. Where MPTCP is not needed, disabling it and restricting network reachability are the fastest risk reductions.

À faire maintenant

1. Inventory Linux systems and confirm whether MPTCP is enabled, loaded, or listening; disable it where it is not required.
2. Use firewall rules and network segmentation to block untrusted access to MPTCP endpoints.
3. Apply Linux kernel and distribution updates as soon as vendors publish fixes, tracking advisories even without a CVE.
4. Monitor for anomalous root-level process creation and unexpected inbound connections to MPTCP services.
5. Validate exposure from untrusted network segments and document any systems that must retain MPTCP.
6. Prepare incident-response steps for potential root compromise, including isolation, credential review, and forensic capture.

Source originale

BleepingComputer