Service crash via truncated watch state
Published Oct 13, 2026 · Updated Oct 13, 2026
State corruption in Xen 4.22 C Xenstore allows guest OS users to crash the service during live update via depth-limited watches. The live-update writer omits two bytes from each watch state record with a specified depth, leaving inconsistent state when the replacement Xenstore reads it. Unprivileged guests can trigger service crashes or corrupted Xenstore data that prevent further domain administration; oxenstored is unaffected.
Summary
What happened
State corruption in Xen 4.22 C Xenstore allows guest OS users to crash the service during live update via depth-limited watches. The live-update writer omits two bytes from each watch state record with a specified depth, leaving inconsistent state when the replacement Xenstore reads it. Unprivileged guests can trigger service crashes or corrupted Xenstore data that prevent further domain administration; oxenstored is unaffected.
The record
- CVE
- CVE-2026-79607
- Published
- Oct 13, 2026
- Updated
- Oct 13, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 13, 2026CVE publishedPublication date reported by the CVE source.
- Oct 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started