CVE-2026-72014
DRBD kernel buffer overflow via malicious data reply causing kernel memory corruption
Is CVE-2026-72014 being exploited?
Not confirmed. CVE-2026-72014 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.68% probability of exploitation in the next 30 days.
How severe is CVE-2026-72014?
CVE-2026-72014 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-72014?
Yes. A fix has been recorded for CVE-2026-72014. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72014 affect?
CVE-2026-72014 affects Linux kernel (DRBD module), DRBD peers and replication clients, Diskless/read-balancing nodes. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72014?
Apply kernel/DRBD updates immediately; restrict/untrust peers and network access to DRBD.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote kernel memory corruption from a crafted DRBD P_DATA_REPLY; may cause crashes or enable privilege escalation.
Immediate action required
- affected>= b411b3637fa71fce9cf2acf0639009500f5892fe and < bca33f5442c3094511719d9db792ce3165d87e76
- affected>= b411b3637fa71fce9cf2acf0639009500f5892fe and < 741a682535deffe9ab7e5c89caf83571efbc9dd9
- affected>= b411b3637fa71fce9cf2acf0639009500f5892fe and < f14e87d7b166490bceb9603b39310e51595d05b9
- affected>= b411b3637fa71fce9cf2acf0639009500f5892fe and < f16866c62656865854106b79bcf6e4ca97a51a92
- affected>= b411b3637fa71fce9cf2acf0639009500f5892fe and < 5f59a8142000f0b8f75c432209ead73c424a745d
- affected>= b411b3637fa71fce9cf2acf0639009500f5892fe and < 38cc4867540ae8beedfe41a1a1a6ed37052c77d6
- affected>= b411b3637fa71fce9cf2acf0639009500f5892fe and < 648d4317326e6aa3f8c05cbf0fd14cc2eba6ca99
- affected>= b411b3637fa71fce9cf2acf0639009500f5892fe and < bd910a7660d280595ef94cb6d193951d855d330f
- affected2.6.33
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.