GPU VulnDB

Database/Kernel, userspace & hypervisor

OpenSSL AES-GCM-SIV: an empty AAD update drops earlier AAD from the authentication tag

CVSS 7.5CVE-2026-88823Kernel, userspace & hypervisorcurated

Impact

In OpenSSL's AES-GCM-SIV, an AAD update of zero length resets all the AAD supplied before it. Any application that feeds AAD in several pieces, one of them empty, produces and accepts tags that do not cover the earlier AAD, so an attacker can forge that data. Re-initialising a context also left AAD from the previous message in place. This only matters for software that uses AES-GCM-SIV directly. TLS does not negotiate this cipher, so ordinary TLS traffic on GPU nodes and control-plane services is not affected. The FIPS modules are not affected.

Who can reach it

Network attacker who can change messages protected by an application that uses OpenSSL AES-GCM-SIV with fragmented AAD that includes an empty fragment. No authentication needed against the protocol itself.

What to do

Update OpenSSL to the release named in the 2026-11-10 OpenSSL advisory, then restart every process that links it. Distribution packages usually need a restart of the dependent services, not a reboot. If you cannot patch, check whether any in-house or third-party software on the fleet calls AES-GCM-SIV. Most stacks do not.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.