GPU VulnDB

Database/Kernel, userspace & hypervisor

OpenSSL: failed PEM_X509_INFO read leaves freed entries in a caller-supplied stack

CVSS 7.7CVE-2026-107493Kernel, userspace & hypervisorcurated

Impact

When a PEM read through PEM_X509_INFO_read_bio_ex() or the related functions fails, OpenSSL frees every X509_INFO entry in the stack the caller passed in, both old and new, but leaves the pointers in place. An application that keeps using that stack then touches freed memory, which can crash it or, in principle, corrupt memory. Malformed PEM data is enough to make the read fail. However, only applications that pass a non-NULL existing stack are affected. OpenSSL itself never does this, including when TLS loads CA certificates, and the OpenSSL team expects very few applications to do so.

Who can reach it

Anyone who can supply malformed PEM data to an application that passes an existing stack to these functions. No authentication is implied, but the attacker cannot make an application use the vulnerable calling pattern.

What to do

Update OpenSSL to the release named in the 2026-11-17 OpenSSL advisory, or to a distro package carrying the listed commits, then restart processes linked against it. No reboot is needed. Most fleet daemons are not exposed because OpenSSL's own callers pass NULL, so this can follow the routine package cycle.

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.