VDB

CVE-2025-38708

CVE-2025-38708 PUBLISHED CVSS 9.8 CRITICAL

drbd: add missing kref_get in handle_write_conflicts

Reported by linux · Published September 4, 2025

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
perf6.12Amazon Linux1:6.12.46-66.121.amzn2023
kernel6.12-libbpfAmazon Linux1:6.12.46-66.121.amzn2023
kernel-libbpf-develAmazon Linux1:6.1.150-174.273.amzn2023

Risk scores

CVSS 3.1
9.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

VendorProductVersions
LinuxLinux668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6, 668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6, 668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6
LinuxLinux4.5, 0, 5.4.297
SiemensSIPLUS S7-1500 CPU 1518-4 PN/DP MFP3.1.5
amazon:2023perf6.120
amazon:2023kernel6.12-libbpf0
amazon:2023kernel-libbpf-devel0
linuxlinux_kernel4.5, 4.5, 4.5
amazon:2023kernel6.12-devel0
amazon:2023bpftool6.120
amazon:2023kernel6.12-libbpf-devel0
amazon:2023kernel-livepatch-6.12.46-66.1210
amazon:2023kernel-libbpf-static0
SiemensSIMATIC CN 41000
amazon:2023kernel-devel0
amazon:2023kernel-tools0
amazon:2023kernel6.12-headers0
amazon:2023kernel-headers0
amazon:2023python3-perf6.120
amazon:2023kernel0
amazon:2023kernel6.12-modules-extra-common0

…and 16 more

Timeline

  • Sep 4, 2025 CVE Published
  • Sep 5, 2025 EPSS Score (30 in total, the first dated here)
  • Dec 18, 2025 PoC Published (2 in total, the first dated here)
  • Feb 2, 2026 Security Advisory (185 in total, the first dated here)
  • Mar 29, 2026 Distribution Patch (172 in total, the first dated here)
  • Jun 9, 2026 Coalition ESS Score
  • Oct 25, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2025-38708
vulnetix vdb fixes CVE-2025-38708

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-38708/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›