CyberSecBulletin
CVE-2026-53068NVD status: Analyzed

Linux: Integer Overflow or Wraparound

Published Updated By the CyberSecBulletin desk

CVE-2026-53068 is a high-severity integer overflow or wraparound vulnerability in Linux, with a CVSS 3.1 base score of 7.1 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 a3a2a9bdc0f9c2d863a5a290cb2d4a565f7268e7, e27b58095d7d3ac72f230e318838dee956258460, 02ff8a7d3d0eecc546b9ab4c07b3d7c65d485583 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.17% 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 a3a2a9bdc0f9c2d863a5a290cb2d4a565f7268e7 or e27b58095d7d3ac72f230e318838dee956258460 or 02ff8a7d3d0eecc546b9ab4c07b3d7c65d485583 or d8a541906860aa3519b1874780d933c766918a7c, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.10.258 or 5.15.209 or 6.1.175 or 6.6.141, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux65ad2392dd6d1691db93e82b08d3311298b9d64a up to, but not including, a3a2a9bdc0f9c2d863a5a290cb2d4a565f7268e7; 65ad2392dd6d1691db93e82b08d3311298b9d64a up to, but not including, e27b58095d7d3ac72f230e318838dee956258460; 65ad2392dd6d1691db93e82b08d3311298b9d64a up to, but not including, 02ff8a7d3d0eecc546b9ab4c07b3d7c65d485583; 65ad2392dd6d1691db93e82b08d3311298b9d64a up to, but not including, d8a541906860aa3519b1874780d933c766918a7c; 65ad2392dd6d1691db93e82b08d3311298b9d64a up to, but not including, 8165e8b28fdf392c2c7412518d602b4f193812a8; 65ad2392dd6d1691db93e82b08d3311298b9d64a up to, but not including, fe1f80f8f6e8611ac6349b9d464e8750443390cf; 65ad2392dd6d1691db93e82b08d3311298b9d64a up to, but not including, 872d923b852705054bc099af663da862fdc1097d; 65ad2392dd6d1691db93e82b08d3311298b9d64a up to, but not including, 779ec12c85c9e4547519e3903a371a3b26a289de; and 1 more rangesa3a2a9bdc0f9c2d863a5a290cb2d4a565f7268e7, e27b58095d7d3ac72f230e318838dee956258460, 02ff8a7d3d0eecc546b9ab4c07b3d7c65d485583, d8a541906860aa3519b1874780d933c766918a7c, 8165e8b28fdf392c2c7412518d602b4f193812a8, fe1f80f8f6e8611ac6349b9d464e8750443390cf
LinuxLinux Kernel5.3 up to, but not including, 5.10.258; 5.11 up to, but not including, 5.15.209; 5.16 up to, but not including, 6.1.175; 6.2 up to, but not including, 6.6.141; 6.7 up to, but not including, 6.12.91; 6.13 up to, but not including, 6.18.33; 6.19 up to, but not including, 7.0.105.10.258, 5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33

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
NoneNothing can be modified.
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:N/A:H. Scored by CNA.

Official description

In the Linux kernel, the following vulnerability has been resolved: drm/komeda: fix integer overflow in AFBC framebuffer size check The AFBC framebuffer size validation calculates the minimum required buffer size by adding the AFBC payload size to the framebuffer offset. This addition is performed without checking for integer overflow. If the addition oveflows, the size check may incorrectly succed and allow userspace to provide an undersized drm_gem_object, potentially leading to out-of-bounds memory access. Add usage of check_add_overflow() to safely compute the minimum required size and reject the framebuffer if an overflow is detected. This makes the AFBC size validation more robust against malformed. Found by Linux Verification Center (linuxtesting.org) with SVACE.

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. Record last changed materially (score, affected products, status or references).

References

Recent Integer Overflow or Wraparound vulnerabilities

Spotted an error? Tell us.