Anybody have a sense of impact and scope of recently released redis security alert? CVE-2025-49844 I see 6x in some of our older xo environments and 7.0.xx in xoa

We have a ticket in but wondering if anybody else has started troubleshooting this yet

Last login: Tue Aug 26 08:08:15 2025 from 10.136.192.170
$ redis-server
3379289:C 07 Oct 2025 11:56:33.844 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3379289:C 07 Oct 2025 11:56:33.844 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=3379289, just started

@edsilber Ticket#7737661 submitted

@olivierlambert said in XCP vm fails to boot after newest kernel applied.:

For such issues, it's a lot better to create a support ticket. We could point you to get more detailed output (or serial) to understand exactly what's causing the boot to fail

Reply

Sure thing, we were just trying to triage this morning. "Yes this seems to be real & Don't update until we know more" bought us a little time until we could move to next steps. Ticket incoming...

We have a ticket from some users who were unable to boot their Xen vms after updating to the newest Red Hat kernel (4.18.0-553.50.1.el8_10.x86_64) That same kernel seems to work ok on VMware. We've seen references to it in the wild https://forums.almalinux.org/t/kernel-panic-4-18-0-553-50-1-el8-10-x86-64-on-xenserver-8-4/5754
We're telling our users to hold off on that patch until we know more.
The xen security advisory is from back in December but looks like the fix implementation has broken something. https://xenbits.xen.org/xsa/advisory-466.html
Any workarounds known?