<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Avx-512 on SoloSoft</title><link>https://www.solosoft.dev/tags/avx-512/</link><description>Recent content in Avx-512 on SoloSoft</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 18 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.solosoft.dev/tags/avx-512/index.xml" rel="self" type="application/rss+xml"/><item><title>Java4Shell Measured: 62 Bytes Past the Buffer, a Four-Line Fix, and a Trigger That Fires Once per JIT Compile</title><link>https://www.solosoft.dev/post/java4shell-cve-2026-114938-measured/</link><pubDate>Wed, 18 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.solosoft.dev/post/java4shell-cve-2026-114938-measured/</guid><description>&lt;p&gt;Java&amp;rsquo;s selling point for twenty years has been that you cannot write past the end of an array. On 17 November 2026, a normal Base64 decode call did exactly that on a stock JDK.&lt;/p&gt;
&lt;p&gt;CVE-2026-114938 — branded Java4Shell by Calif.io — is a heap buffer overflow in HotSpot&amp;rsquo;s x86-64 Base64 intrinsic, fixed by Oracle in an out-of-band Critical Security Patch Update and scored 8.1 by the vendor and 9.2 by the researcher. Within four hours the Hacker News thread had 461 points and 120 comments, most of them asking the same question: is this real, and am I affected?&lt;/p&gt;
&lt;p&gt;That question is answerable with a download and a twenty-line Java file. This host has the required CPU (an AMD EPYC 9354P, Zen 4, &lt;code&gt;avx512vbmi&lt;/code&gt; present), so I fetched six runtimes, ran the published proof of concept, and then wrote probes that the write-up does not contain. The short version: the bug is real, the vendor and researcher descriptions are both landing on the same code path, and the published PoC understates the collision — it decodes into a 4,096-byte array so the overflow stays inside the array it is measuring. Put the destination at its natural size and the same call silently rewrites the next object&amp;rsquo;s header.&lt;/p&gt;</description></item></channel></rss>