Vulnary
← back to the feed
Critical· 9.8official fix available

CVE-2025-38708

A bug in the DRBD kernel module caused a use‑after‑free when two nodes wrote to the same sector at the same time. The flaw can crash the kernel, leading to a denial of service. The issue has been fixed in recent kernel releases.

publishedSep 4, 2025
last modifiedJul 30, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
27th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 29, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Linux kernel users running DRBD with the two‑primaries feature enabled, such as Debian 11.0 systems that use DRBD for high‑availability storage.

02

Real-world impact

An attacker who can trigger concurrent writes to the same sector on a DRBD cluster could cause the kernel to crash, taking the system offline. The crash could also provide a foothold for further exploitation if the attacker can gain code execution during the crash.

03

Why this severity

The CVSS score of 9.8 reflects that the vulnerability can be exploited remotely without authentication, requires no user interaction, and compromises confidentiality, integrity, and availability of the entire system.

04

What to do about it

official fix available
recommended steps
  1. 01Upgrade the Linux kernel to a version that includes the DRBD patch for CVE‑2025‑38708.
  2. 02Reboot the system to load the updated kernel.

NVD description indicates the issue has been resolved in the Linux kernel.

05

Timeline

  1. Sep 4, 2025 · Sep 4, 2025
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 30, 2026 · 7d ago
    Advisory updated
    The NVD record was last revised.
  3. Jul 30, 2026 · 6d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

NVD advisory ↗Search advisories ↗
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →