News for hackers. Stuff that matters.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by cjbprime on Tuesday November 17, 2026 @05:36PM (#50539263)
Wouldn't it be prudent for someone to patch even if they aren't running their code on an AVX512 system right this moment? They could be running on one.. next moment.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by Banditoz on Tuesday November 17, 2026 @05:45PM (#50539343)
Sure, but I think it brings it down from "patch immediately" severity, to just "bump the JDK with next service deploy" severity.

Or, do running machines often have their CPU changed from under them without much notice?

Re:Java4Shell: RCE in OpenJDK when processing Base64 by stackskipton on Tuesday November 17, 2026 @05:55PM (#50539423)
Depends on the company and deployment method. As Ops person, I generally don't think much about rolling out different Kubernetes Nodes and what SKU I select. So yes, you could be running on one node type today and tomorrow I upgrade the nodes under you.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by xmodem on Tuesday November 17, 2026 @06:42PM (#50539846)
We’re using a second-tier cloud provider’s managed Kubernetes offering, and in investigating our level of exposure to this, I just learned that there is variance within a node pool on whether AVX-512 is available.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by jamesfinlayson on Tuesday November 17, 2026 @11:47PM (#50541993)
This - I remember taking a suggestion to cat cpuinfo as part of container start in AWS and you do get a bit of variety as you'd expect (five year old processors last time I checked as well).
Re:Java4Shell: RCE in OpenJDK when processing Base64 by Sohcahtoa82 on Tuesday November 17, 2026 @06:39PM (#50539816)
> Or, do running machines often have their CPU changed from under them without much notice?

I dunno about other cloud providers, but I know AWS can move your EC2 VM from one system to another transparently. There is a server ID you can get from the metadata, but unless you're checking it frequently, you can be moved without ever being aware.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by PhilipRoman on Tuesday November 17, 2026 @07:11PM (#50540131)
Question is if they expose it to the guest. Many (most?) cloud platforms will make the guest see the lowest common denominator, specifically to avoid angry customers when their working setup suddenly breaks.

In the case of transparent migration, I think it's basically a must. No JIT (or even libc probably) is going to support CPU features changing at runtime.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by johnbellone on Tuesday November 17, 2026 @08:02PM (#50540529)
You’ll need to restart the guest.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by acdha on Tuesday November 17, 2026 @10:16PM (#50541422)
Not for a routine migration, but they typically keep it inside the same processor family for this reason.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by Sohcahtoa82 on Wednesday November 18, 2026 @02:00AM (#50542789)
Not true.

AWS migrates live instances to new CPUs without needing to stop or reboot the guest.

When a migration is needed, the hypervisor begins copying blocks of memory to the new system, keeping track of what blocks are written inside the guest during the migration. Once enough has been copied, it hibernates the guest, copies the remaining memory, then wakes it in the new system. On a system that isn't writing to large swaths of memory, it can take only a few milliseconds. To the guest, it might appear that the CPU froze for a tiny bit of time, which could easily just look like a neighbor got noisy.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by mike_hearn on Wednesday November 18, 2026 @03:10AM (#50543278)
Yes, but that's irrelevant here because the CPUID report won't change across live migrations.

Consider what would happen if you were live migrated from a machine with AVX512 to one without. Your app would suddenly start crashing with SIGILL for no apparent reason. So, live migrations always preserve the apparent CPU feature set. If you started on a machine without AVX512 then until the VM is rebooted you will remain on such a (virtual) machine.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by tecleandor on Wednesday November 18, 2026 @06:14AM (#50544852)
But why would you live migrate between instances with a different instruction set? You'd need to emulate the missing instruction sets then...