CVE-2026-72014: drbd: reject data replies with an out-of-range payload size

Published Aug 15, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

drbd: reject data replies with an out-of-range payload size

recvdlessread() receives a PDATAREPLY from a peer into the bio of an outstanding read request. The peer-supplied payload length reaches it as the signed int datasize, and two peer-controlled inputs can make it negative. With a negotiated data-integrity-alg the digest length is subtracted first, so a reply whose payload is smaller than the digest underflows datasize. With no integrity algorithm (the default) datasize is assigned from the unsigned h95/h100 wire length and drbdd() never bounds it for a payload-carrying command, so a length above INTMAX casts it negative; this path needs no non-default feature. The bio receive loop then computes expect = mint(int, datasize, bvlen), which is negative, and drbdrecvallwarn(mapped, expect) receives with a sizet of SIZEMAX into the first mapped page.

The sibling receive path readinblock() is not affected: it uses an unsigned size and rejects it against DRBDMAXBIOSIZE before receiving. Reject a data reply whose size is negative after the optional digest subtraction, covering both triggers.

Impact: a malicious or man-in-the-middle DRBD peer copies attacker-chosen bytes past a bio page in the receiver, corrupting kernel memory. A node that reads from its peer (a diskless node, or read-balancing to the peer) is exposed in the default configuration; data-integrity-alg is not required.

Affected Software

1 affected component
Linus Torvalds Linux Kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    No special feature is required for the vulnerable path: the issue exists in the default configuration (no data-integrity-alg / default integrity behavior). Ensure the kernel fix (“Reject a data reply whose size is negative after the optional digest”) is applied for DRBD P_DATA_REPLY handling.

    DRBD data-integrity-alg = not required (default path remains affected per description)

Event History

Aug 15, 2026
CVE Published
via MITRE·05:51 AM
Data Sourced
via MITRE·05:51 AM
Description
Data Sourced
via NVD·06:21 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-72014?

The severity of CVE-2026-72014 is rated at 80.

2

What types of systems are affected by CVE-2026-72014?

CVE-2026-72014 affects systems running the Linux kernel utilizing DRBD.

3

How do I fix CVE-2026-72014?

To fix CVE-2026-72014, upgrade to the patched version of the Linux kernel that addresses this vulnerability.

4

What is the main issue described in CVE-2026-72014?

CVE-2026-72014 describes a vulnerability where data replies with out-of-range payload sizes can be incorrectly processed.

5

Is CVE-2026-72014 an easy vulnerability to exploit?

CVE-2026-72014 may require specific conditions and knowledge of the system to exploit effectively.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203