CVE-2025-38708
Linux Kernel use-after-free
- Published4 Sept 2025
Description
In the Linux kernel, the following vulnerability has been resolved: drbd: add missing kref_get in handle_write_conflicts With `two-primaries` enabled, DRBD tries to detect "concurrent" writes and handle write conflicts, so that even if you write to the same sector simultaneously on both nodes, they end up with the identical data once the writes are completed. In handling "superseeded" writes, we forgot a kref_get, resulting in a premature drbd_destroy_device and use after free, and further to kernel crashes with symptoms. Relevance: No one should use DRBD as a random data generator, and apparently all users of "two-primaries" handle concurrent writes correctly on layer up. That is cluster file systems use some distributed lock manager, and live migration in virtualization environments stops writes on one node before starting writes on the other node. Which means that other than for "test cases", this code path is never taken in real life. FYI, in DRBD 9, things are handled differently nowadays. We still detect "write conflicts", but no longer try to be smart about them. We decided to disconnect hard instead: upper layers must not submit concurrent writes. If they do, that's their fault.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
- https://git.kernel.org/stable/c/00c9c9628b49e368d140cfa61d7df9b8922ec2a8
- https://git.kernel.org/stable/c/0336bfe9c237476bd7c45605a36ca79c2bca62e5
- https://git.kernel.org/stable/c/3a896498f6f577e57bf26aaa93b48c22b6d20c20
- https://git.kernel.org/stable/c/46e3763dcae0ffcf8fcfaff4fc10a90a92ffdd89
- https://git.kernel.org/stable/c/57418de35420cedab035aa1da8a26c0499b7f575
- https://git.kernel.org/stable/c/7d483ad300fc0a06f69b019dda8f74970714baf8
References
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://git.kernel.org/stable/c/00c9c9628b49e368d140cfa61d7df9b8922ec2a8
- https://git.kernel.org/stable/c/0336bfe9c237476bd7c45605a36ca79c2bca62e5
- https://git.kernel.org/stable/c/3a896498f6f577e57bf26aaa93b48c22b6d20c20
- https://git.kernel.org/stable/c/46e3763dcae0ffcf8fcfaff4fc10a90a92ffdd89
- https://git.kernel.org/stable/c/57418de35420cedab035aa1da8a26c0499b7f575
- https://git.kernel.org/stable/c/7d483ad300fc0a06f69b019dda8f74970714baf8
- https://git.kernel.org/stable/c/810cd546a29bfac90ed1328ea01d693d4bd11cb1
- https://git.kernel.org/stable/c/84ef8dd3238330d1795745ece83b19f0295751bf
and 3 more references
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-38708 being actively exploited?
CVE-2025-38708 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.38%.
How severe is CVE-2025-38708?
CVE-2025-38708 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.38% probability of exploitation.
Which products are affected by CVE-2025-38708?
Affected products include Debian Linux, Linux Kernel.
How do I fix CVE-2025-38708?
Upgrade affected software to a fixed version, for example Linux Kernel 5.4.297 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-38708 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.