Xenbleed: Xen Guest to Dom0 Escape
Comments on “Xenbleed: Xen Guest to Dom0 Escape”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
CodeAnt AI researchers report a Xen grant-copy flaw, fixed in XSA-523 on November 3, that lets a guest with kernel-level control read and write dom0 memory. A batch cache reused locked domains after a failed grant lookup, skipping the check limiting direct frame numbers to the caller's own memory. They reproduced it on XenServer 9 and ran reversible code in dom0's kernel, on one pCPU and one kernel image. Xen lists no mitigation. Dates, severity scores and the 2015 origin come from CodeAnt alone.
Why it ranked
No. 1 of 139 with a score of 0.76. The panel rated it highest on technical depth (0.96) and new information (0.92), lowest on audience breadth (0.67).
- AI judgeJudge 2claude-haiku-5-5
- Detailed, primary-source security write-up of a critical hypervisor guest-to-dom0 escape with reproduction details and CVEs; highly relevant to infrastructure builders, though narrower than a universal landmark.
- AI judgeJudge 3gpt-5.6-luna
- A highly technical, reproducible hypervisor escape with concrete root cause, exploit chain, impact, affected versions, CVEs, disclosure timeline, and fixes. It is directly actionable for Xen operators and security engineers, with only minor promotional framing.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.76total under rubric v2.3
- Significance0.78
- Reader interest0.88
- Audience breadth0.67
- Practical relevance0.77
- Substantiated0.90
- Technical depth0.96
- New information0.92
- Counts against: Promotional0.08
- Counts against: Overclaim0.30
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.65 | 0.80 | 0.90 | 0.78 | 0.25 | +0.24 | +0.188 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.75 | 0.93 | 0.95 | 0.88 | 0.20 | +0.26 | +0.228 |
| Audience breadthHow many people who build technology does it concern? | 0.60 | 0.80 | 0.62 | 0.67 | 0.20 | +0.13 | +0.087 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.59 | 0.80 | 0.90 | 0.77 | 0.30 | +0.22 | +0.168 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.91 | 0.85 | 0.95 | 0.90 | 0.10 | +0.05 | +0.045 |
| Technical depthHow technically substantive is it? | 1.00 | 0.90 | 0.98 | 0.96 | 0.10 | +0.05 | +0.048 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.87 | 0.90 | 0.99 | 0.92 | 0.12 | +0.05 | +0.046 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.06 | 0.10 | 0.08 | 0.08 | 0.04 | −0.19 | −0.015 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.49 | 0.20 | 0.20 | 0.30 | 0.29 | −0.11 | −0.033 |
| Sum of contributions | +0.763 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.763 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-05/1/"><img src="https://rubric.hrih.si/badge/2026-11-05/1.svg" alt="Ranked #1 on Rubric, 5 Nov 2026" width="231" height="28"></a>Claim check
Claim check: 1 matches source · 3 no source given · 4 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Couldn’t checkNumber
A January 2015 grant-copy performance change made guest networking on Xen up to 25 percent faster.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “In January 2015, a patch made guest networking on Xen up to 25 percent faster”
The source says No passage could be compared.
Source cited by the article: github.com/xen-project/xen/commit/d28f42f2703e483116bafd2b0b76a32af67d83ad
Couldn’t checkDate
The grant-copy performance change that introduced the flaw was committed on January 29, 2015.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “The flaw dates to a grant-copy performance change committed on January 29, 2015”
The source says No passage could be compared.
Source cited by the article: github.com/xen-project/xen/commit/d28f42f2703e483116bafd2b0b76a32af67d83ad
No source givenNumber
The flaw stayed open for 4,296 days and affected kernel code in any guest on Xen 4.6 or later, allowing read and write access to dom0.
The article gives no link or citation for it.
The article says “That door stayed open for 4,296 days. Kernel code in any guest on Xen 4.6 or later could use it to read and write dom0”
The source says No source to compare with.
Couldn’t checkDate
Xen published the fix as XSA-523 on November 3, 2026, after a two-week embargo, and the patches credit CodeAnt AI Security Research.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Xen publishes XSA-523 after a two-week embargo. Both patches carry a Reported-by line for CodeAnt AI Security Research”
The source says No passage could be compared.
Source cited by the article: xenbits.xen.org/xsa/advisory-523.html
Matches sourceCausal conclusion
XSA-523 covers two defects in the grant-copy cache, CVE-2026-102703 and CVE-2026-102704, both stemming from reusing cached state without validating everything that made it valid.
The cited source says the same thing.
The article says “XSA-523 covers two defects introduced into this cache. Both came from the same design mistake”
The source says “The conditions on when to re-validate the internal data were not correct in some cases”
Source cited by the article: xenbits.xen.org/xsa/advisory-523.html
No source givenNumber
CodeAnt AI assessed both CVEs at CVSS 9.3 Critical (v3.1) and 9.4 Critical (v4.0).
The article gives no link or citation for it.
The article says “our CVSS assessment for both CVEs: 9.3 Critical (v3.1) and 9.4 Critical (v4.0”
The source says No source to compare with.
Couldn’t checkVersion
The official patch adds a check requiring b->have_grant == has_gref in gnttab_copy_buf_valid() before accepting a cached numeric match.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “gnttab_copy_buf_valid() needed to require b->have_grant == has_gref before accepting a cached numeric match. The official patch adds that mode check”
The source says No passage could be compared.
Source cited by the article: xenbits.xen.org/xsa/xsa523-1.patch
No source givenDate
Xen's security team replied the day after the October 13 report that the issue was already known and a fix was being prepared.
The article gives no link or citation for it.
The article says “replied the next day: the issue was already known to them, a fix was being prepared, and they offered us independent discovery credit”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 2 pts, not on front page
Recorded for context only, checked 5 Nov 2026, 05:46 UTC. It played no part in the ranking.