CVE-2025-38708
Vulnerability Scoring
Analysis In Progress
CVE-2025-38708 Vulnerability Analysis & Exploit Details
CVE-2025-38708
Attack Complexity Details
-
Attack Complexity:
Attack Complexity Analysis In Progress
-
Attack Vector:
Attack Vector Under Analysis
-
Privileges Required:
None
No authentication is required for exploitation.
-
Scope:
Impact is confined to the initially vulnerable component.
-
User Interaction:
None
No user interaction is necessary for exploitation.
CVE-2025-38708 Details
Status: Awaiting Analysis
Last updated: 🕠 05 Sep 2025, 17:47 UTC
Originally published on: 🕓 04 Sep 2025, 16:15 UTC
Time between publication and last update: 1 days
CVSS Release:
CVE-2025-38708 Vulnerability Summary
CVE-2025-38708: 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.
Assessing the Risk of CVE-2025-38708
Access Complexity Graph
The exploitability of CVE-2025-38708 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).
Exploitability Analysis for CVE-2025-38708
No exploitability data is available for CVE-2025-38708.
Understanding AC and PR
A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.
Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.
Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.
CVSS Score Breakdown Chart
Above is the CVSS Sub-score Breakdown for CVE-2025-38708, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.
CIA Impact Analysis
Below is the Impact Analysis for CVE-2025-38708, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.
-
Confidentiality:
None
CVE-2025-38708 does not compromise confidentiality.
-
Integrity:
None
CVE-2025-38708 does not impact data integrity.
-
Availability:
None
CVE-2025-38708 does not affect system availability.
CVE-2025-38708 References
External References
- 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
- https://git.kernel.org/stable/c/9f53b2433ad248cd3342cc345f56f5c7904bd8c4
CWE Common Weakness Enumeration
Unknown
Protect Your Infrastructure against CVE-2025-38708: Combat Critical CVE Threats
Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.
Other 5 Recently Published CVEs Vulnerabilities
- CVE-2025-48042 – Incorrect Authorization vulnerability in ash-project ash allows Exploiting Incorrectly Configured Access Control Security Levels. This vulnerabilit...
- CVE-2025-39734 – In the Linux kernel, the following vulnerability has been resolved: Revert "fs/ntfs3: Replace inode_trylock with inode_lock" This reverts commit ...
- CVE-2025-39733 – In the Linux kernel, the following vulnerability has been resolved: team: replace team lock with rtnl lock syszbot reports various ordering issue...
- CVE-2025-39732 – In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix sleeping-in-atomic in ath11k_mac_op_set_bitrate_mask() ath1...
- CVE-2025-39731 – In the Linux kernel, the following vulnerability has been resolved: f2fs: vm_unmap_ram() may be called from an invalid context When testing F2FS ...