WeSearch

Mad Bugs: QEMU and UTM Escape

Calif· ·9 min read · 0 reactions · 0 comments · 27 views
#cybersecurity#qemu#virtualization#vulnerability#macos
Mad Bugs: QEMU and UTM Escape
TL;DR · WeSearch summary

Researchers discovered a guest-to-host escape vulnerability in QEMU's virtio-gpu device that affects UTM when running in emulation mode with VNC enabled. The exploit leverages a memory disclosure via the VNC server, allowing a compromised guest to read host heap memory and achieve code execution. Although patched in QEMU 11.0.0, the fix was not backported to the 10.x series used by UTM, leaving prior versions exposed.

Key facts
About this source

Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.

Original article
Calif · Calif
Read full at Calif →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherCalif
Canonical URLhttps://blog.calif.io/p/mad-bugs-qemu-and-utm-escape
Publication timeTue, 28 Apr 2026 20:28:34 +0000
Retrieval time2026-04-28T20:44:39.819Z
Last seen2026-04-28T20:44:39.819Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster7VHBIJ6RzqH6
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

MAD Bugs: QEMU and UTM EscapeIn which the guest VNCs into its own host and watches the heap like a screensaver.Apr 28, 20268ShareThis post is part of MAD Bugs, our Month of AI-Discovered Bugs, where we pair frontier models with human expertise and publish whatever falls out.Before we dive in, one piece of news. Dion Blazakis and Stefan Esser are joining Calif. Dion just escaped left the fruit company, so we thought it'd be fitting to drop a macOS VM escape exploit.Our targets are QEMU and UTM. QEMU is the open-source machine emulator and virtualizer that powers most Linux virtualization stacks: libvirt, OpenStack, KubeVirt, and the KVM side of many cloud platforms. UTM is the App-Store-friendly macOS and iOS frontend that wraps QEMU.

Excerpt limited to ~120 words for fair-use compliance. The full article is at Calif.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Calif