Linux: Integer Overflow or Wraparound
CVE-2026-68257 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 b88ffe6593607364a8c06a48c6f29e55437cdf8e, abce3276c57e36c955627307469b9f009057a467, 865532d54eb57b660b1cb1b0e1755776ce21b849 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.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to b88ffe6593607364a8c06a48c6f29e55437cdf8e or abce3276c57e36c955627307469b9f009057a467 or 865532d54eb57b660b1cb1b0e1755776ce21b849 or 2b0386d4293920e690c0e017708f999b93cc729b, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 325aa07165394b8e866ffe9ec1d4c99d9195b2f2 up to, but not including, b88ffe6593607364a8c06a48c6f29e55437cdf8e; d15deafab5d722afb9e2f83c5edcdef9d9d98bd1 up to, but not including, abce3276c57e36c955627307469b9f009057a467; d15deafab5d722afb9e2f83c5edcdef9d9d98bd1 up to, but not including, 865532d54eb57b660b1cb1b0e1755776ce21b849; d15deafab5d722afb9e2f83c5edcdef9d9d98bd1 up to, but not including, 2b0386d4293920e690c0e017708f999b93cc729b; 63600103d2ac5c09fdeec5b931b396e4e0efd5d8; 6.12.59 up to, but not including, 6.12.101; 6.17.9 up to, but not including, 6.18; 6.18 | b88ffe6593607364a8c06a48c6f29e55437cdf8e, abce3276c57e36c955627307469b9f009057a467, 865532d54eb57b660b1cb1b0e1755776ce21b849, 2b0386d4293920e690c0e017708f999b93cc729b, 6.12.101, 6.18 |
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: drm/amdkfd: fix 32-bit overflow in CWSR total size calculation total_cwsr_size was computed in 32-bit before being used as a BO/SVM allocation size. With large ctx_save_restore_area_size and debug_memory_size multiplied by the XCC count, the product can wrap, yielding an undersized CWSR save area that firmware later overruns. Promote total_cwsr_size to u64 and use check_add_overflow()/ check_mul_overflow() in both kfd_queue_acquire_buffers() and kfd_queue_release_buffers(). (cherry picked from commit 319f7e13423ae3f486b9aea82f9ad2d6af0ee608)
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
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Recent Integer Overflow or Wraparound vulnerabilities
- 8.1 High severity
- 7.5 High severity
- 7.8 High severity
- 9.8 Critical severity
- 7.8 High severity
- 8.8 High severity
Spotted an error? Tell us.