Xen maintains the _GTF_{read,writ}ing bits as appropriate, to inform the guest that a grant is in use. A guest is expected not to modify the grant details while it is in use, whereas the guest is free to modify/reuse the grant entry when it is not in use. Under some circumstances, Xen will clear the status bits too early, incorrectly informing the guest that the grant is no longer in use. A guest may prematurely believe that a granted frame is safely private again, and reuse it in a way which contains sensitive information, while the domain on the far end of the grant is still using the grant. Xen 4.9, 4.8, 4.7, 4.6, and 4.5 are affected.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alpine Linux | — | Upgrade xen | Oct 30, 2017 | Aug 15, 2017 |
| Debian | — | Upgrade xen | Sep 13, 2017 | Aug 15, 2017 |
| Redhat_linux | — | No solution exists | Jul 9, 2025 | Aug 15, 2017 |
| Suse | — | Upgrade xen-doc-htmlUpgrade xen-tools-domUUpgrade xen-develUpgrade xen-toolsUpgrade xen-libsUpgrade xen-libs-32bitUpgrade xen-kmp-paeUpgrade xen-kmp-defaultUpgrade xen-doc-pdfUpgrade xen | Sep 1, 2017 | Aug 15, 2017 |
| Ubuntu | — | Upgrade xen | Nov 19, 2024 | Aug 15, 2017 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub