9.8

CVE-2025-38708: debian debian_linux Use After Free

CVSS: 9.8v3.1CriticalModified
AliasesUBUNTU-CVE-2025-38708DEBIAN-CVE-2025-38708
Published 04-09-2025Last modified 15-10-2026

Vulnerability summary

CVE-2025-38708 is a critical (CVSS 9.8) Use After Free vulnerability in debian debian_linux. EPSS estimates a 0.38% chance of exploitation in the next 30 days, higher than 30.4% of scored vulnerabilities.

Overall risk
70/100
0100
High · default modelHow is this calculated?
CVSS score
9.8/10
010
Critical · v3.1 (CVE.org)
EPSS score
0.38%
0%100%
Low · +0.01 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 30 · Related 25

Timeline

  1. 04-09-2025
    PublishedVulnerability first disclosed.
  2. 15-10-2026
    Last modifiedVulnerability information updated.

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 metrics

4 scores · 4 sources · 1 version

EPSS trend

Probability

0.38%

Chance of exploitation in the next 30 days

Percentile

30%

Versus all other CVEs

30-day change

+0.01 pp

From 0.37% on 19-09-2026

19-09-202619-10-2026
EPSS score
0.38%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Ubuntu147 products
  • linuxAll versions (No fix recorded) | < 5.15.0-163.173 | < 6.8.0-100.100
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-awsAll versions (No fix recorded) | < 5.15.0-1097.104 | < 6.8.0-1046.49
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Debian2 products
  • linux< 6.1.153-1 | < 6.12.43-1 | < 6.16.3-1
  • debian_linuxEOL11.0
Linux2 products
  • linux≥ 668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6, < 0336bfe9c237476bd7c45605a36ca79c2bca62e5 | ≥ 668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6, < 810cd546a29bfac90ed1328ea01d693d4bd11cb1 | ≥ 668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6, < 84ef8dd3238330d1795745ece83b19f0295751bf | ≥ 668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6, < 57418de35420cedab035aa1da8a26c0499b7f575 | ≥ 668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6, < 9f53b2433ad248cd3342cc345f56f5c7904bd8c4 | ≥ 668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6, < 7d483ad300fc0a06f69b019dda8f74970714baf8 | ≥ 668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6, < 46e3763dcae0ffcf8fcfaff4fc10a90a92ffdd89 | ≥ 668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6, < 3a896498f6f577e57bf26aaa93b48c22b6d20c20 | ≥ 668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6, < 00c9c9628b49e368d140cfa61d7df9b8922ec2a8 | 4.5
  • linux_kernel≥ 4.5, < 5.4.297 | ≥ 5.5, < 5.10.241 | ≥ 5.11, < 5.15.190 | ≥ 5.16, < 6.1.149 | ≥ 6.2, < 6.6.103 | ≥ 6.7, < 6.12.43 | ≥ 6.13, < 6.15.11 | ≥ 6.16, < 6.16.2

3 vendors · 151 products

References

43 links
Show all 43 references