Kernel crash via missing DRBD device reference
Published Sep 4, 2025 · Updated Aug 5, 2026
Use-after-free in Linux DRBD and affected Siemens firmware allows remote attackers to crash the kernel during conflicting writes. The handle_write_conflicts path processes a superseded write without taking a device reference, so drbd_destroy_device can free the device before later access. Reachability requires two-primaries mode and simultaneous writes to the same sector; normal clustered storage coordinates writers, so the disclosed result is a kernel crash.
Summary
What happened
Use-after-free in Linux DRBD and affected Siemens firmware allows remote attackers to crash the kernel during conflicting writes. The handle_write_conflicts path processes a superseded write without taking a device reference, so drbd_destroy_device can free the device before later access. Reachability requires two-primaries mode and simultaneous writes to the same sector; normal clustered storage coordinates writers, so the disclosed result is a kernel crash.
The record
- CVE
- CVE-2025-38708
- Published
- Sep 4, 2025
- Updated
- Aug 5, 2026
- Vendor
- Siemens
- Product
- SIPLUS S7-1500 CPU 1518-4 PN/DP MFP
- Classifications
- CWE-416, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 4, 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