Kernel compromise via premature vsock socket release
Published Feb 27, 2025 · Updated Aug 5, 2026
Use-after-free in Linux kernel vsock and affected Siemens GNU/Linux subsystems allows local users to read or write kernel memory or crash the system. During transport reassignment, transport->release() removes a still-bound socket, and __vsock_bind() later drops its reference count to zero before accessing it. A local low-privileged process must create and rebind a vsock socket across a transport change; successful exploitation compromises the kernel.
Summary
What happened
Use-after-free in Linux kernel vsock and affected Siemens GNU/Linux subsystems allows local users to read or write kernel memory or crash the system. During transport reassignment, transport->release() removes a still-bound socket, and __vsock_bind() later drops its reference count to zero before accessing it. A local low-privileged process must create and rebind a vsock socket across a transport change; successful exploitation compromises the kernel.
The record
- CVE
- CVE-2025-21756
- Published
- Feb 27, 2025
- Updated
- Aug 5, 2026
- Vendor
- Siemens
- Product
- SIPLUS S7-1500 CPU 1518-4 PN/DP MFP
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 27, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=V3.1.5 <*
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo