CyberSecBulletin
CVE-2025-68794NVD status: Deferred

Linux: Integer Overflow or Wraparound

Published Updated By the CyberSecBulletin desk

CVE-2025-68794 is a critical-severity integer overflow or wraparound vulnerability in Linux, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions ce20f49ac9194cf81a77f01d1c316d7c17ae753c, 275b37a1e5c2c8abd313e8075f6aec9a349f291b, b8c9f25fd84328c5fcc4f70c6d1e8f1d4787eaac 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.69% chance of exploitation within 30 days, higher than 53% of scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update Linux to ce20f49ac9194cf81a77f01d1c316d7c17ae753c or 275b37a1e5c2c8abd313e8075f6aec9a349f291b or b8c9f25fd84328c5fcc4f70c6d1e8f1d4787eaac or 82b60ffbb532d919959702768dca04c3c0500ae5, whichever matches your release line, or a later version.
  2. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux9dc55f1389f9569acf9659e58dd836a9c70df217 up to, but not including, ce20f49ac9194cf81a77f01d1c316d7c17ae753c; 9dc55f1389f9569acf9659e58dd836a9c70df217 up to, but not including, 275b37a1e5c2c8abd313e8075f6aec9a349f291b; 9dc55f1389f9569acf9659e58dd836a9c70df217 up to, but not including, b8c9f25fd84328c5fcc4f70c6d1e8f1d4787eaac; 9dc55f1389f9569acf9659e58dd836a9c70df217 up to, but not including, 82b60ffbb532d919959702768dca04c3c0500ae5; 9dc55f1389f9569acf9659e58dd836a9c70df217 up to, but not including, 12053695c8ef5410e8cc6c9ed4c0db9cd9c82b3e; 9dc55f1389f9569acf9659e58dd836a9c70df217 up to, but not including, 142194fb21afe964d2d194cab1fc357cbf87e899; 9dc55f1389f9569acf9659e58dd836a9c70df217 up to, but not including, 7aa6bc3e8766990824f66ca76c19596ce10daf3e; 4.19ce20f49ac9194cf81a77f01d1c316d7c17ae753c, 275b37a1e5c2c8abd313e8075f6aec9a349f291b, b8c9f25fd84328c5fcc4f70c6d1e8f1d4787eaac, 82b60ffbb532d919959702768dca04c3c0500ae5, 12053695c8ef5410e8cc6c9ed4c0db9cd9c82b3e, 142194fb21afe964d2d194cab1fc357cbf87e899

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
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
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:N/AC:L/PR:N/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: adjust read range correctly for non-block-aligned positions iomap_adjust_read_range() assumes that the position and length passed in are block-aligned. This is not always the case however, as shown in the syzbot generated case for erofs. This causes too many bytes to be skipped for uptodate blocks, which results in returning the incorrect position and length to read in. If all the blocks are uptodate, this underflows length and returns a position beyond the folio. Fix the calculation to also take into account the block offset when calculating how many bytes can be skipped for uptodate blocks.

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: yes, 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.