Database/Kernel, userspace & hypervisor

Xen on AMD Family 17h / Hygon Family 18h - guest SSBD selection: Setting Speculative Store Bypass Disable on AMD Family
Impact
Setting Speculative Store Bypass Disable on AMD Family 17h and Hygon Family 18h has to be coordinated at the physical core level, and Xen's logic did not do that correctly. The consequence is that a guest which asked for SSBD protection may not actually get it - or may have it silently disabled by a sibling. A tenant hardening itself against Spectre-v4 gets a mitigation that is not in force, which is worse than knowing it is off.
Who can reach it
Cross-guest speculative execution between VMs sharing a physical core.
What to do
Fixed in Xen (XSA-431). Hypervisor update plus host reboot. Verify per-guest that SSBD is genuinely active afterwards rather than trusting the requested setting.
References
Related entries
- SSSD autofs responder: improper buffer offset during request parsing causes out-of-bounds read and crashCVE-2026-104029 · SSSD autofs responder (request buffer offset calculation)Low
- VMware ESX: insufficient logging lets a malicious administrator perform operations without an audit recordCVE-2026-41709 · VMware ESX (administrative operation audit logging)Low
- OpenSSH sshd: restrict in authorized_keys does not disable tunnel forwarding as documentedCVE-2026-106586 · OpenSSH sshd (restrict keyword in authorized_keys, tunnel forwarding)Low
- OpenSSH sshd: restrict keyword in authorized_keys did not cover tunnel forwardingCVE-2026-73283 · OpenSSH sshd (authorized_keys restrict keyword vs tunnel forwarding)Low
- OpenSSH sshd: GSSAPI credentials and authentication state persist after a failed attemptCVE-2026-106553 · OpenSSH sshd (GSSAPIAuthentication credential and state handling)Low
- QEMU / KVM / Xen (VENOM): VENOM: out-of-bounds write in the virtual Floppy Disk ControllerCVE-2015-3456 · QEMU / KVM / Xen (VENOM)Low
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.