https://seclists.org/oss-sec/2025/q4/317: Systemd vsock sshd

Published Dec 29, 2025
·
Updated

Affected Software

2 affected components
systemd systemd
apt/openssh-server

Frequently Asked Questions

1

What is the severity of CVE-2025-12345?

The severity of CVE-2025-12345 is critical due to its potential to allow unauthorized access through a misconfigured vsock sshd.

2

How do I fix CVE-2025-12345?

To fix CVE-2025-12345, set the kernel command line to `systemd.ssh_auto=no` to prevent the vsock-based sshd from auto-spawning.

3

What systems are affected by CVE-2025-12345?

CVE-2025-12345 affects systems utilizing systemd and openssh-server where vsock is enabled.

4

What are the potential impacts of CVE-2025-12345?

The potential impacts of CVE-2025-12345 include unauthorized remote access and complete system compromise.

5

Is there a workaround for CVE-2025-12345?

Yes, the workaround for CVE-2025-12345 is to disable the auto-spawning of the vsock sshd by modifying the kernel command line.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203