-
Update done here in my home lab, no issue
-
Only one of my two systems will take the complete update, but that one is working just fine.
The other which I had used in the past as a test server for XOSTOR will not install the sm-2.30.8-12.1.xcpng8.2.x86_64 package looking for a dependency on sm-linstor and not finding it.
-
JeffBerntsen Indeed, the update for XOSTOR is not ready yet. It will be before we release the updates, but I forgot about you testers
-
stormi Not a problem. I just wanted to make sure I hadn't done something wrong. As it is, the system is working with all of the updates but that one in place.
-
stormi Update went well on my two node homelab. VMs and basic operations work as expected. Let's see how things go over the next days. Keep up the good work!
-
stormi Updated all my normal 8.2 systems updated. All working normally.
-
Thanks everyone for your tests!
We just published the updates: https://xcp-ng.org/blog/2024/06/17/june-2024-security-and-maintenance/
-
stormi Are these going to be pushed to 8.3 or just part of the final release?
-
CJ Everything that is relevant for XCP-ng 8.3 is either already built and ready to be pushed (you can pull from
xcp-ng-candidatesif you want it already), or being built/tested. -
New security update candidate (xen, xapi, xsconsole)
Two new XSAs were published on 16th of July.
- XSA-458 guests which have a multi-vector MSI capable device passed through to them can leverage the vulnerability.
- XSA-459 impacts systems running Xapi v3.249.x, which means any up to date XCP-ng 8.2. Note this requires heavy crafting and likely social engineering on the attacker side, see the XSA's "VULNERABLE SYSTEMS" section for more details.
SECURITY UPDATES
xen-*:- Fix XSA-458 - double unlock in x86 guest IRQ handling. When passing through a multi-vector MSI capable device to a guest, an attacker could use an error handling path that could lead to the issue, no exploitations results have been ruled out: Denial of Service (DoS), crashes, information leaks, or elevation of privilege could all be possible.
xapi,xsconsole:- Fix XSA-459 - Xapi: Metadata injection attack against backup/restore functionality. A malicious guest can manipulate its disk to appear to be a metadata
backup, then having about a 50% chance of appearing ahead of a legitimate metadata backup. The more disks the guest has, the higher the chances of this happening are.
- Fix XSA-459 - Xapi: Metadata injection attack against backup/restore functionality. A malicious guest can manipulate its disk to appear to be a metadata
Test on XCP-ng 8.2
yum clean metadata --enablerepo=xcp-ng-testing yum update "xen-*" "xapi-*" xsconsole --enablerepo=xcp-ng-testing rebootThe usual update rules apply: pool coordinator first, etc.
Versions:
xen: xen-4.13.5-9.40.2.xcpng8.2xapi: xapi-1.249.36-1.2.xcpng8.2xsconsole: xsconsole-10.1.13-1.2.xcpng8.2
What to test
Normal use and anything else you want to test.
Test window before official release of the update
~ 1 day because of security updates.
-
I suppose I need to be a bit more patient
No packages marked for update -
I indeed forgot to wait for mirrors to sync before posting, my bad, should be good soon
-
bleader Updated my two node homelab and everything seems to work as expected. Let's see how things go over the next days.
-
bleader Updated an running on newer and older Intel machines. Running normally so far.
-
Tested in my own lab, no issues so far
-
Update published https://xcp-ng.org/blog/2024/07/18/july-2024-security-updates/
Thank you everyone for your tests!
-
bleader 2 production polls updated via RPU without issues.
-
New security update candidates (xen, microcode_ctl)
A new XSA was published on August 14th 2024.
Intel published an updated microcode on August 13th 2024.
- XSA-460 passing through some PCI devices after guest creation could lead to any kind of security issue (DoS, privilege escalation, information leak,…) the actual risk depends on the systems and the devices passed through.
- XSA-461 some pass-through use cases when on one or more device when they share resources are actually not possible to be made secure. This XSA updates the Xen documentation to reflect that.
SECURITY UPDATES
xen-*:- Fix XSA-460 - error handling in x86 IOMMU identity mapping. The handling of errors in the case of mapping Reserved Memory Regions was flawed, potentially keeping the mapping in place, this could allow guests to access memory region they should not be allowed to access. These mapping are typically used when doing pass-through of legacy USB emulation.
- Document XSA-461 - PCI device pass-through with shared resources Files. According to the Xen Project security team, PCI pass-through of devices that share ressources is not possible to be made safe. This updates the documentation to reflect it. Look at the "MITIGATION" section of the XSA for more information regarding the safe cases.
microcode_ctl: Security updates from Intel:- INTEL-SA-01083
- INTEL-SA-01118
- INTEL-SA-01100
- INTEL-SA-01038
- INTEL-SA-01046
- Plus fixes for a lot of functional issues, see the Release Notes for more details.
Test on XCP-ng 8.2
yum clean metadata --enablerepo=xcp-ng-candidates yum update "xen-*" microcode_ctl --enablerepo=xcp-ng-candidates rebootThe usual update rules apply: pool coordinator first, etc.
Versions:
xen: 4.13.5-9.40.3.xcpng8.2microcode_ctl: 2.1-26.xs29.3.xcpng8.2
What to test
Normal use and anything else you want to test. Feedback about PCI pass-through is also welcome.
Test window before official release of the update
~ 2 day because of security updates.
-
bleader Installed and running on pools of 8.2.1 systems.
-
bleader They're installed and running well on my test lab systems.
