<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mptcp on CuraSec</title><link>https://curasec.metacog.co.kr/tags/mptcp/</link><description>Recent content in Mptcp on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 31 Oct 2026 16:03:46 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/mptcp/index.xml" rel="self" type="application/rss+xml"/><item><title>Critical Linux kernel MPTCP flaw enables unauthenticated remote root</title><link>https://curasec.metacog.co.kr/insights/2026-10-31-critical-linux-kernel-flaw-allows-remote-root-attacks-on-mpt/</link><pubDate>Sat, 31 Oct 2026 16:03:46 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-31-critical-linux-kernel-flaw-allows-remote-root-attacks-on-mpt/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> Severity is high (unauthenticated remote root), but enrichment signals are absent — no KEV, no confirmed public PoC, no active exploitation. Audit whether MPTCP listeners are running on exposed servers and schedule kernel patching as soon as a fix is available; consider disabling MPTCP if it is not operationally required.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No IOCs, no confirmed in-the-wild exploitation, and no ATT&amp;amp;CK-mappable TTPs are published yet; there is nothing to hunt or detect at this stage. Watch for follow-on reporting with exploitation evidence before writing detections.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>