CyberSecBulletin
CVE-2026-68158NVD status: Received

Linux: Integer Overflow or Wraparound

Published Updated By the CyberSecBulletin desk

CVE-2026-68158 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 2ceee3b77b83052648c40fef965f836fd7699d26, e4473751cc37db41f3f7da25d64a23e0c74570f1, f6961070c326bd158c38fa48756cde2bd78c4aaa 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.71% chance of exploitation within 30 days, higher than 54% of scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update Linux to 2ceee3b77b83052648c40fef965f836fd7699d26 or e4473751cc37db41f3f7da25d64a23e0c74570f1 or f6961070c326bd158c38fa48756cde2bd78c4aaa or 05c90e059269f087becfcce23348496085835c29, 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
LinuxLinux930c532869774ebf8af9efe9484c597f896a7d46 up to, but not including, 2ceee3b77b83052648c40fef965f836fd7699d26; 930c532869774ebf8af9efe9484c597f896a7d46 up to, but not including, e4473751cc37db41f3f7da25d64a23e0c74570f1; 930c532869774ebf8af9efe9484c597f896a7d46 up to, but not including, f6961070c326bd158c38fa48756cde2bd78c4aaa; 930c532869774ebf8af9efe9484c597f896a7d46 up to, but not including, 05c90e059269f087becfcce23348496085835c29; 930c532869774ebf8af9efe9484c597f896a7d46 up to, but not including, 143ba49ead77ec483c0326f8aaad8649874e99c4; 930c532869774ebf8af9efe9484c597f896a7d46 up to, but not including, 1732d89dfcd74f6fde9ce70900d316c4a151c153; 930c532869774ebf8af9efe9484c597f896a7d46 up to, but not including, bee4b5b53e7bff0467fd916cc44c9b190733c6bd; 930c532869774ebf8af9efe9484c597f896a7d46 up to, but not including, 98917a499ec7064c14fc56d180a4fd636fc2784c; and 17 more ranges2ceee3b77b83052648c40fef965f836fd7699d26, e4473751cc37db41f3f7da25d64a23e0c74570f1, f6961070c326bd158c38fa48756cde2bd78c4aaa, 05c90e059269f087becfcce23348496085835c29, 143ba49ead77ec483c0326f8aaad8649874e99c4, 1732d89dfcd74f6fde9ce70900d316c4a151c153

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: libceph: Fix multiplication overflow in decode_new_up_state_weight() If a message of type CEPH_MSG_OSD_MAP contains a (maliciously) corrupted osdmap, out-of-bounds memory accesses may occur in decode_new_up_state_weight(). This happens because the bounds check for the new_state part is based on calculating its length depending on a len value read from the incoming message. This calculation may overflow leading to an incorrect bounds check. Subsequently, out-of-bounds reads may occur when decoding this part. This patch switches the multiplication to use check_mul_overflow() to abort processing the osdmap if an overflow occurred. Therefore, osdmaps/messages containing large values for len that result in a multiplication overflow are treated as invalid. [ idryomov: rename new_state_len -> new_state_item_size, formatting ]

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.