CyberSecBulletin
CVE-2026-68145NVD status: Received

Linux: Integer Overflow or Wraparound

Published Updated By the CyberSecBulletin desk

CVE-2026-68145 is a high-severity integer overflow or wraparound vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 48829622212f6b8f49155889aecc818ba28ba680, fb4fad9105c88b1d82f1b3c39e3b6abea8249af6, 7037e7bdcd26f46c080b8ce307dee5cb471c4b7c as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.14% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 48829622212f6b8f49155889aecc818ba28ba680 or fb4fad9105c88b1d82f1b3c39e3b6abea8249af6 or 7037e7bdcd26f46c080b8ce307dee5cb471c4b7c or c5b6a48a8a716a7730e39af1cad083dc4ec955ce, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux4ce02c67972211be488408c275c8fbf19faf29b3 up to, but not including, 48829622212f6b8f49155889aecc818ba28ba680; 4ce02c67972211be488408c275c8fbf19faf29b3 up to, but not including, fb4fad9105c88b1d82f1b3c39e3b6abea8249af6; 4ce02c67972211be488408c275c8fbf19faf29b3 up to, but not including, 7037e7bdcd26f46c080b8ce307dee5cb471c4b7c; 4ce02c67972211be488408c275c8fbf19faf29b3 up to, but not including, c5b6a48a8a716a7730e39af1cad083dc4ec955ce; 4ce02c67972211be488408c275c8fbf19faf29b3 up to, but not including, 9c7d8f7c8994c790fca501dc45ce66e7356cbe05; 6.648829622212f6b8f49155889aecc818ba28ba680, fb4fad9105c88b1d82f1b3c39e3b6abea8249af6, 7037e7bdcd26f46c080b8ce307dee5cb471c4b7c, c5b6a48a8a716a7730e39af1cad083dc4ec955ce, 9c7d8f7c8994c790fca501dc45ce66e7356cbe05

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.

Official description

In the Linux kernel, the following vulnerability has been resolved: iomap: fix out-of-bounds bitmap_set() with zero-length range ifs_set_range_dirty() and ifs_set_range_uptodate() compute last_blk as (off + len - 1) >> i_blkbits. When off is 0 and len is 0, the unsigned subtraction underflows to SIZE_MAX, producing a huge last_blk and nr_blks value that causes bitmap_set() to write far beyond the ifs->state allocation. Regarding ifs_set_range_uptodate(), it is temporarily safe because len cannot be passed in as 0. However, for ifs_set_range_dirty() this is reachable from __iomap_write_end(): when copy_folio_from_iter_atomic() returns 0 (e.g. user buffer fault) and the folio is already uptodate, the guard at the top of __iomap_write_end() does not trigger because !folio_test_uptodate() is false, and iomap_set_range_dirty() is called with copied == 0. Add a !len guard to both functions before the computation, so that a zero-length range is a no-op.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Integer Overflow or Wraparound

The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

How developers prevent this class of flaw

  • Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. If possible, choose a language or compiler that performs automatic bounds checking.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Use libraries or frameworks that make it easier to handle numbers without unexpected consequences. Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++).

More Integer Overflow or Wraparound vulnerabilities (CWE-190)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Integer Overflow or Wraparound vulnerabilities

Spotted an error? Tell us.