Database/Kernel, userspace & hypervisor
libssh SCP client: malicious server can write files outside the client's working directory
Impact
A malicious SCP server can return unexpected paths that make a libssh-based client write files outside the intended working directory - the same class of flaw as OpenSSH's CVE-2019-6111. An attacker-controlled or compromised endpoint can therefore drop executables or configuration files where the client user will later run or read them, turning a routine file pull into code execution under that account. On a GPU fleet the relevant clients are automated: dataset and checkpoint fetchers, job wrappers, and configuration tooling that pull from remote hosts under a shared service account, often into directories that are on PATH or sourced at login. Red Hat rates it moderate, and it requires the client to actually initiate a transfer against a hostile server.
Who can reach it
Network, outbound and requiring user or job interaction: an SCP transfer must be initiated from the libssh client to a server the attacker controls or has compromised. No credentials on the client host are needed.
What to do
Update libssh to 0.12.0 or 0.11.4, or apply your distribution's backport - Red Hat has shipped RHSA-2026:18160 and RHSA-2026:18683 for RHEL and OpenShift Container Platform 4. This is a shared-library package upgrade, so any long-running process linked against libssh must be restarted to pick it up; no reboot or node drain. Prefer sftp over the legacy scp protocol in automation where you can.
References
Related entries
- Linux kernel (drivers/pci/hotplug): A power fault on a PCIe hotplug slot latches a sticky status bit that the hardirqCVE-2021-47617 · Linux kernel (drivers/pci/hotplug)Medium
- Linux kernel (drivers/iommu/arm/arm-smmu-v3): A process using SVA that unmaps memory drives a flood of SMMU rangeCVE-2023-52484 · Linux kernel (drivers/iommu/arm/arm-smmu-v3)Medium
- libvirt: negative array length in RPC deserialization crashes libvirtdCVE-2024-2494 · libvirt RPC server (array allocation before non-negative length check)Medium
- libvirt: race in the RPC client event loop gives a stack use-after-free reachable through virtproxydCVE-2024-4418 · libvirt virtNetClientIOEventLoop (stack use-after-free in the RPC client path, reachable via virtproxyd)Medium
- libvirt: zero-byte allocation corner case lets read-only clients crash virtinterfacedCVE-2024-8235 · libvirt virtinterfaced (NULL dereference in the interface-listing APIs)Medium
- QEMU e1000: guest-triggered stack overflow in the loopback receive path crashes the host QEMU processCVE-2025-12464 · QEMU e1000 network device (e1000_receive_iov loopback path)Medium
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.