Answer in brief
CVE-2025-38708 records a Unknown severity vulnerability in drbd: add missing kref_get in handle_write_conflicts. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC CN 4100 (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2025-38708 records a Unknown severity vulnerability in drbd: add missing kref_get in handle_write_conflicts. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC CN 4100 (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC CN 4100 (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 <0336bfe9c237476bd7c45605a36ca79c2bca62e5 || >=668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 <810cd546a29bfac90ed1328ea01d693d4bd11cb1 || >=668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 <84ef8dd3238330d1795745ece83b19f0295751bf || >=668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 <57418de35420cedab035aa1da8a26c0499b7f575 || >=668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 <9f53b2433ad248cd3342cc345f56f5c7904bd8c4 || >=668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 <7d483ad300fc0a06f69b019dda8f74970714baf8 || >=668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 <46e3763dcae0ffcf8fcfaff4fc10a90a92ffdd89 || >=668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 <3a896498f6f577e57bf26aaa93b48c22b6d20c20 || >=668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 <00c9c9628b49e368d140cfa61d7df9b8922ec2a8 | 0336bfe9c237476bd7c45605a36ca79c2bca62e5, 810cd546a29bfac90ed1328ea01d693d4bd11cb1, 84ef8dd3238330d1795745ece83b19f0295751bf, 57418de35420cedab035aa1da8a26c0499b7f575, 9f53b2433ad248cd3342cc345f56f5c7904bd8c4, 7d483ad300fc0a06f69b019dda8f74970714baf8, 46e3763dcae0ffcf8fcfaff4fc10a90a92ffdd89, 3a896498f6f577e57bf26aaa93b48c22b6d20c20, 00c9c9628b49e368d140cfa61d7df9b8922ec2a8 |
| Linux/Linuxgeneric | 4.5 | Not reported |
| Siemens/SIMATIC CN 4100generic | >=0 <V5.0 | V5.0 |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.5 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric | >=V3.1.5 <* | * |
| Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.5 <* | * |
Published upstream
Sep 4, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC CN 4100 (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 <0336bfe9c237476bd7c45605a36ca79c2bca62e5 || >=668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 <810cd546a29bfac90ed1328ea01d693d4bd11cb1 || >=668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 <84ef8dd3238330d1795745ece83b19f0295751bf || >=668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 <57418de35420cedab035aa1da8a26c0499b7f575 || >=668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 <9f53b2433ad248cd3342cc345f56f5c7904bd8c4 || >=668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 <7d483ad300fc0a06f69b019dda8f74970714baf8 || >=668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 <46e3763dcae0ffcf8fcfaff4fc10a90a92ffdd89 || >=668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 <3a896498f6f577e57bf26aaa93b48c22b6d20c20 || >=668700b40a7c8727bbd2b3fd4fd22e0ce3f1aeb6 <00c9c9628b49e368d140cfa61d7df9b8922ec2a8 | 0336bfe9c237476bd7c45605a36ca79c2bca62e5, 810cd546a29bfac90ed1328ea01d693d4bd11cb1, 84ef8dd3238330d1795745ece83b19f0295751bf, 57418de35420cedab035aa1da8a26c0499b7f575, 9f53b2433ad248cd3342cc345f56f5c7904bd8c4, 7d483ad300fc0a06f69b019dda8f74970714baf8, 46e3763dcae0ffcf8fcfaff4fc10a90a92ffdd89, 3a896498f6f577e57bf26aaa93b48c22b6d20c20, 00c9c9628b49e368d140cfa61d7df9b8922ec2a8 |
| Linux/Linuxgeneric | 4.5 | Not reported |
| Siemens/SIMATIC CN 4100generic | >=0 <V5.0 | V5.0 |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.5 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric | >=V3.1.5 <* | * |
| Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.5 <* | * |
Published upstream
Sep 4, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.