Skip to main content
VulnerabilityPublished Updated

CVE-2026-72014: Linux kernel · Integer Overflow

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in f16866c62656865854106b79bcf6e4ca97a51a92 : patch Linux kernel as a priority.

Data as of 26 Oct 2026, 17:30 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in f16866c62656865854106b79bcf6e4ca97a51a92, f14e87d7b166490bceb9603b39310e51595d05b9, bd910a7660d280595ef94cb6d193951d855d330f +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ b411b3637fa71fce9cf2acf0639009500f5892fe, < f16866c62656865854106b79bcf6e4ca97a51a92
Fixed in
  • f16866c62656865854106b79bcf6e4ca97a51a92
LinuxLinuxAffected
  • ≥ b411b3637fa71fce9cf2acf0639009500f5892fe, < f14e87d7b166490bceb9603b39310e51595d05b9
Fixed in
  • f14e87d7b166490bceb9603b39310e51595d05b9
LinuxLinuxAffected
  • ≥ b411b3637fa71fce9cf2acf0639009500f5892fe, < bd910a7660d280595ef94cb6d193951d855d330f
Fixed in
  • bd910a7660d280595ef94cb6d193951d855d330f
LinuxLinuxAffected
  • ≥ b411b3637fa71fce9cf2acf0639009500f5892fe, < bca33f5442c3094511719d9db792ce3165d87e76
Fixed in
  • bca33f5442c3094511719d9db792ce3165d87e76
LinuxLinuxAffected
  • ≥ b411b3637fa71fce9cf2acf0639009500f5892fe, < 741a682535deffe9ab7e5c89caf83571efbc9dd9
Fixed in
  • 741a682535deffe9ab7e5c89caf83571efbc9dd9
LinuxLinuxAffected
  • ≥ b411b3637fa71fce9cf2acf0639009500f5892fe, < 648d4317326e6aa3f8c05cbf0fd14cc2eba6ca99
Fixed in
  • 648d4317326e6aa3f8c05cbf0fd14cc2eba6ca99

Description

In the Linux kernel, the following vulnerability has been resolved: drbd: reject data replies with an out-of-range payload size recv_dless_read() receives a P_DATA_REPLY from a peer into the bio of an outstanding read request. The peer-supplied payload length reaches it as the signed int data_size, 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 data_size. With no integrity algorithm (the default) data_size is assigned from the unsigned h95/h100 wire length and drbdd() never bounds it for a payload-carrying command, so a length above INT_MAX casts it negative; this path needs no non-default feature. The bio receive loop then computes expect = min_t(int, data_size, bv_len), which is negative, and drbd_recv_all_warn(mapped, expect) receives with a size_t of SIZE_MAX into the first mapped page. The sibling receive path read_in_block() is not affected: it uses an unsigned size and rejects it against DRBD_MAX_BIO_SIZE 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.

References

Community reviews

Loading reviews…