Exploiting System Management Mode with a very long interrupt
WhiteDawn
45 points
12 comments
August 10, 2026
Related Discussions
Found 5 related stories in 150.4ms across 13,334 title embeddings via pgvector HNSW
- KVM: x86: Unconditionally reset MMU context when emulating INIT (CVE-2026-99312) Kozmik1 · 183 pts · November 18, 2026 · 46% similar
- Multiple remote code execution vulnerabilities in danfoss sm-800A rros · 18 pts · November 11, 2026 · 46% similar
- Big Fish: Exploiting a 37-Year-Old Kernel Bug in OpenBSD rs_rs_rs_rs_rs · 177 pts · October 16, 2026 · 46% similar
- One parser, two bugs, many routers: Exploiting Broadcom WiFi across eCos, Linux tosh · 14 pts · October 18, 2026 · 44% similar
- Systems and Delays vinhnx · 48 pts · July 26, 2026 · 42% similar
Discussion Highlights (5 comments)
nazgulsenpai
I'm amused at the lengths the readme goes to in order to drive home the fact that this needs to be a LOOOOOOOOOOOOOOOOOOOONG instruction, including the unnecessarily long code block illustration. The topic is interesting anyway, but that makes it way more entertaining.
londons_explore
Unclear why there is a 1 second timeout at all. Presumably the patch for that will be to make it an infinity timeout.
kmeisthax
...huh, I was wondering why serial machine code prankster xoreaxeaxeax was keeping lists of extremely long-running instructions. Hopefully this is at least only possible in kernel mode, right? Right?!
mike_hearn
The designers of the firmware anticipate this attack but punt it to the vendor, apparently: // // Platform implementor should choose a timeout value appropriately: [snip] // - The timeout value must be longer than longest possible IO operation in the system
Liftyee
I don't know much about the specifics of CPU architecture apart from the existence of assembly and different modes. Either way the explanation was still entertaining and interesting. smiiiiiiii