Summary
This update for xen fixes the following issues:
Security issues fixed:
- CVE-2026-62437: x86: DMs may cause mem leak by IRQ binding (bsc#1276838).
- CVE-2026-79602: x86: improper handling of HVM emulation return codes (bsc#1276839).
- CVE-2026-79603: unconditionally do TLB flushing ahead of page scrubbing (bsc#1276841).
- CVE-2026-79609: x86: XPTI may break on huge-memory systems (bsc#1283321).
- CVE-2026-79610: grant-table: double version change race (bsc#1283322).
- CVE-2026-79611: VMX: VMentry failure with branch tracing and blocked states (bsc#1283323).
- CVE-2026-102700: gnttab: cache-flush handling may cause page reference leak (bsc#1283325).
- CVE-2026-102703,CVE-2026-102704: arbitrary read/write via grant copy (bsc#1288663).
Non security issue fixed:
- Update to Xen 4.18.6 security bug fix release (bsc#1027519).
Fixed packages 2
| Release | Package | Fixed in |
|---|---|---|
| SUSE · SLES 15 SP6 Linux Enterprise Server 15 SP6-LTSS | xen | 4.18.6_03-150600.3.56.1 |
| SUSE · SLES for SAP 15 SP6 Linux Enterprise Server for SAP Applications 15 SP6 | xen | 4.18.6_03-150600.3.56.1 |
Vulnerabilities 9
-
High 8.8
x86: improper handling of HVM emulation return codes
A guest with a PCI device assigned that has at least a BAR on the IO port space can trigger a BUG() in Xen.
-
High 8.8
x86: XPTI may break on huge-memory systems
XPTI (Xen Page Table Isolation) was introduced to mitigate Meltdown (CVE-2017-5754, one aspect of XSA-254). This involves copying 64-bit PV guest page table entries from guest-chosen root page tables to the Xen- chosen one which is in actual use by hardware. …
-
High 8.8
grant-table: double version change race
XSA-501 was about issues with v1 -> v2 and v2 -> v1 changes racing certain other grant table operations. Sadly a v2 -> v1 -> v2 change has yet another effect which wasn't accounted for: During the first change, status pages would be freed. During the second c…
-
Medium 6.5
x86: DMs may cause mem leak by IRQ binding
When guests are terminated, various pieces of cleanup need carrying out. The cleaning up of PCI devices which were assigned to guests, and the associated removal of tracking structures for IRQs used by the devices occurs relatively early in the process. Unfor…
-
Medium 5.5
VMX: VMentry failure with branch tracing and blocked states
For XSA-308 logic was introduced, as VMX VMEntry checks do not like the exact combination of state which occurs when #DB in intercepted, Single Stepping is active, and blocked by STI/MovSS is active, despite this being a legitimate state to be in. The resulti…
-
Medium 4.7
gnttab: cache-flush handling may cause page reference leak
With its original introduction, GNTTAB_cache_flush was made available uniformly. XSA-232 (CVE-2017-14318) then covered an omitted NULL pointer check, yet the addition of that check failed to adjust the subsequent error path. That error path fails to drop a pa…
-
Medium 4.4
arbitrary read/write via grant copy
[This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] A common access pattern is a batch of Grant Copy operations acting on adjacent address ranges in the same source or destination pa…
-
Medium 4.4
arbitrary read/write via grant copy
[This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] A common access pattern is a batch of Grant Copy operations acting on adjacent address ranges in the same source or destination pa…
-
Medium 4.3
Unconditionally do TLB flushing ahead of page scrubbing
x86 PV guests can free memory pages while still keeping a stale TLB entry pointing to them. A TLB flush is only issued by Xen (if needed) when the page is re-used. Since it's possible for the page to be scrubbed ahead of the TLB flush, there's a window where …
References
-
report
https://bugzilla.suse.com/1027519
-
report
https://bugzilla.suse.com/1276838
-
report
https://bugzilla.suse.com/1276839
-
report
https://bugzilla.suse.com/1276841
-
report
https://bugzilla.suse.com/1283321
-
report
https://bugzilla.suse.com/1283322
-
report
https://bugzilla.suse.com/1283323
-
report
https://bugzilla.suse.com/1283325
-
report
https://bugzilla.suse.com/1288663
-
web
https://www.suse.com/security/cve/CVE-2026-102700
-
web
https://www.suse.com/security/cve/CVE-2026-102703
-
web
https://www.suse.com/security/cve/CVE-2026-102704
-
web
https://www.suse.com/security/cve/CVE-2026-62437
-
web
https://www.suse.com/security/cve/CVE-2026-79602
-
web
https://www.suse.com/security/cve/CVE-2026-79603
-
web
https://www.suse.com/security/cve/CVE-2026-79609
-
web
https://www.suse.com/security/cve/CVE-2026-79610
-
web
https://www.suse.com/security/cve/CVE-2026-79611