CyberSecBulletin
CVE-2026-53110NVD status: Modified

Linux: Integer Overflow or Wraparound

Published Updated By the CyberSecBulletin desk

CVE-2026-53110 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 edc90a12073b9a530064a99945c183dde120cb99, 44c4f999b03f55debb1a0c5ab5c1796895a1adf8, 366b0e05ee24f5ba62bdc7ec1346038258b9a797 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.12% 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 edc90a12073b9a530064a99945c183dde120cb99 or 44c4f999b03f55debb1a0c5ab5c1796895a1adf8 or 366b0e05ee24f5ba62bdc7ec1346038258b9a797 or 834918a77be51419383bf1dda9f02b81ecf26b34, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.6.141 or 6.12.91 or 6.18.33 or 7.0.10, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux528eb2cb87bc1353235a6384696b4849bde8b0ba up to, but not including, edc90a12073b9a530064a99945c183dde120cb99; 528eb2cb87bc1353235a6384696b4849bde8b0ba up to, but not including, 44c4f999b03f55debb1a0c5ab5c1796895a1adf8; 528eb2cb87bc1353235a6384696b4849bde8b0ba up to, but not including, 366b0e05ee24f5ba62bdc7ec1346038258b9a797; 528eb2cb87bc1353235a6384696b4849bde8b0ba up to, but not including, 834918a77be51419383bf1dda9f02b81ecf26b34; 528eb2cb87bc1353235a6384696b4849bde8b0ba up to, but not including, 202e42e4aa890172366354b233c42c73107a3f59; 6.3edc90a12073b9a530064a99945c183dde120cb99, 44c4f999b03f55debb1a0c5ab5c1796895a1adf8, 366b0e05ee24f5ba62bdc7ec1346038258b9a797, 834918a77be51419383bf1dda9f02b81ecf26b34, 202e42e4aa890172366354b233c42c73107a3f59
LinuxLinux Kernel6.3 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.106.6.141, 6.12.91, 6.18.33, 7.0.10

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: s390/bpf: Zero-extend bpf prog return values and kfunc arguments s390x ABI requires callers to zero-extend unsigned arguments and sign-extend signed arguments, and callees to zero-extend unsigned return values and sign-extend signed return values. s390 BPF JIT currently implements only sign extension. Fix this omission and implement zero extension too.

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.