CyberSecBulletin
CVE-2026-68108NVD status: Received

Linux: Integer Overflow or Wraparound

Published Updated By the CyberSecBulletin desk

CVE-2026-68108 is a high-severity integer overflow or wraparound vulnerability in Linux, with a CVSS 3.1 base score of 8.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 893db20383800cfe92e638705984eebb13bc81a5, a07430abd556de3707adfcadcc60db3fa64e4b2b, a6d7065b91a14790980ce6f4960db0ca8c3c9940 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 893db20383800cfe92e638705984eebb13bc81a5 or a07430abd556de3707adfcadcc60db3fa64e4b2b or a6d7065b91a14790980ce6f4960db0ca8c3c9940 or 7eebef042c12dfe0568593ee6a8926d16505925e, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxf1689ec1b0b1256d0e69653cd4aaeee44aafdf5c up to, but not including, 893db20383800cfe92e638705984eebb13bc81a5; f1689ec1b0b1256d0e69653cd4aaeee44aafdf5c up to, but not including, a07430abd556de3707adfcadcc60db3fa64e4b2b; f1689ec1b0b1256d0e69653cd4aaeee44aafdf5c up to, but not including, a6d7065b91a14790980ce6f4960db0ca8c3c9940; f1689ec1b0b1256d0e69653cd4aaeee44aafdf5c up to, but not including, 7eebef042c12dfe0568593ee6a8926d16505925e; f1689ec1b0b1256d0e69653cd4aaeee44aafdf5c up to, but not including, 00c311a13d225266800c712f2b7db2711c6897de; f1689ec1b0b1256d0e69653cd4aaeee44aafdf5c up to, but not including, 186bfdc4e26d019b2e7570cb121964a1d89b2e5b; 4.2893db20383800cfe92e638705984eebb13bc81a5, a07430abd556de3707adfcadcc60db3fa64e4b2b, a6d7065b91a14790980ce6f4960db0ca8c3c9940, 7eebef042c12dfe0568593ee6a8926d16505925e, 00c311a13d225266800c712f2b7db2711c6897de, 186bfdc4e26d019b2e7570cb121964a1d89b2e5b

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
ChangedThe attack can reach beyond the vulnerable component into other systems.
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:C/C:H/I:H/A:H. Scored by CNA.

Official description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vce: fix integer overflow in image size Fix a security vulnerability where malicious VCE command streams with oversized dimensions (e.g. 65536×65536) cause 32-bit integer overflow, wrapping the calculated buffer size to 0. This bypasses validation and allows GPU firmware to perform out-of-bound memory access. The fix uses 64-bit arithmetic to detect overflow and rejects invalid dimensions before they reach the hardware. V2: remove redundant check V3: modify max height value V4: remove size64 (cherry picked from commit cbe408dba581755ad1279a487ec786d8927d778d)

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.