Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-38708drbd: add missing kref_get in handle_write_conflicts

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.

Timeline

  1. ID reserved

    By Linux

  2. · 5 months later

    Published

  3. · 14 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38708, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.40% · top 66% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Affected products

  • Linux · Linux

    • affected 668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 – < 0336bfe9c237476bd7c45605a36ca79c2bca62e5
    • affected 668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 – < 810cd546a29bfac90ed1328ea01d693d4bd11cb1
    • affected 668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 – < 84ef8dd3238330d1795745ece83b19f0295751bf
    • affected 668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 – < 57418de35420cedab035aa1da8a26c0499b7f575
    • affected 668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 – < 9f53b2433ad248cd3342cc345f56f5c7904bd8c4
    • affected 668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 – < 7d483ad300fc0a06f69b019dda8f74970714baf8
    • affected 668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 – < 46e3763dcae0ffcf8fcfaff4fc10a90a92ffdd89
    • affected 668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 – < 3a896498f6f577e57bf26aaa93b48c22b6d20c20
    • affected 668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 – < 00c9c9628b49e368d140cfa61d7df9b8922ec2a8
  • Linux · Linux

    • affected 4.5
    • unaffected < 4.5
    • unaffected 5.4.297 – ≤ 5.4.*
    • unaffected 5.10.241 – ≤ 5.10.*
    • unaffected 5.15.190 – ≤ 5.15.*
    • unaffected 6.1.149 – ≤ 6.1.*
    • unaffected 6.6.103 – ≤ 6.6.*
    • unaffected 6.12.43 – ≤ 6.12.*
    • unaffected 6.15.11 – ≤ 6.15.*
    • unaffected 6.16.2 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References13

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38708 badge
[![CVE-2025-38708](https://cveledger.app/badge/CVE-2025-38708.svg)](https://cveledger.app/cve/CVE-2025-38708)

Record last updated .