Database/Kernel, userspace & hypervisor
libssh: unchecked OpenSSL error can leave a partially initialized ChaCha20 context in use
Impact
When libssh sets up the ChaCha20 cipher through OpenSSL, an allocation failure returns an OpenSSL error code that aliases SSH_OK, so libssh does not notice the failure and continues with a partially initialized cipher context. Red Hat describes the result as undefined behavior, including compromised confidentiality and integrity of the session or a crash. Reaching it requires the attacker to exhaust heap space first, which is why the record scores attack complexity as high - this is not a drive-by. It matters on a fleet because libssh sits under management and orchestration paths rather than interactive logins: libvirt's SSH transport, automation tooling, and anything in the Red Hat and OpenShift stack that links it. A session whose integrity silently degrades on a control path is worse than one that fails closed.
Who can reach it
A network peer of a libssh-based SSH client or server who can also drive the process to heap exhaustion. No authentication is required per the vector, but the memory-pressure precondition makes this hard to trigger deliberately.
What to do
Red Hat has shipped errata for RHEL 9, RHEL 10 and OpenShift Container Platform 4.13 - apply the libssh package update from the RHSA matching your release. Anything already running against the old shared library keeps using it, so restart the services that link libssh (libvirtd and management or automation daemons) after the update. No node drain or reboot is implied by the record.
References
Related entries
- Linux kernel ibmvfc: a malicious VIO server leaks kernel memory through an unclamped target countCVE-2026-31464 · Linux kernel ibmvfc (IBM Power virtual FC discover-targets response)High
- OpenSSH scp: file fetched as root with -O and without -p can land setuid or setgidCVE-2026-35385 · OpenSSH scp (legacy SCP protocol mode, -O without -p)High
- Linux kernel x86/ftrace: dynamic trampoline mis-relocates per-cpu call-depth accounting, crashing the hostCVE-2026-64235 · Linux kernel x86 ftrace dynamic trampolines (CALL_DEPTH_ACCOUNT %rip-relative relocation)High
- Linux SLUB: krealloc __GFP_ZERO guarantee broken when red zoning is enabled without user trackingCVE-2026-64368 · Linux kernel SLUB allocator (init-on-alloc zeroing under SLAB_RED_ZONE)High
- Linux SUNRPC: unchecked percpu_counter_init leaves nfsd running on NULL per-cpu statsCVE-2026-89547 · Linux kernel SUNRPC (__svc_create per-pool percpu_counter init)High
- Linux NFSD: filecache shutdown race leaks nfsd_file objects and their stateCVE-2026-89667 · Linux kernel NFSD filecache (shrinker/GC/fsnotify vs per-net shutdown)High
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.