<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Spectre-V2 on CuraSec</title><link>https://curasec.metacog.co.kr/tags/spectre-v2/</link><description>Recent content in Spectre-V2 on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 07 Aug 2026 00:21:58 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/spectre-v2/index.xml" rel="self" type="application/rss+xml"/><item><title>INTERRUPT INJECTION Bypasses Spectre v2 Mitigations on Linux x86</title><link>https://curasec.metacog.co.kr/insights/2026-08-07-new-interrupt-injection-attack-can-bypass-spectre-v2-defense/</link><pubDate>Fri, 07 Aug 2026 00:21:58 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-07-new-interrupt-injection-attack-can-bypass-spectre-v2-defense/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> MIT CSAIL research shows a timing gap in branch-predictor sanitization can be re-poisoned by a local unprivileged process, defeating default Spectre v2 mitigations on AMD Zen 2 and Intel; no patch or workaround is available yet, but engineers running multi-tenant Linux workloads should track vendor microcode and kernel responses as they emerge.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>