CyberSecBulletin
CVE-2026-68125NVD status: Received

Linux: Integer Overflow or Wraparound

Published Updated By the CyberSecBulletin desk

CVE-2026-68125 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 from the same local network by an unauthenticated attacker, without any action from a user. The record lists versions f27ce82eb04960465df71634b196a48a4ecafd50, 2d6b42a61373144298070668fddf06efe79cf2ff, ec7e62d77193131227df49d654d118fdf5a59892 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.32% 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 f27ce82eb04960465df71634b196a48a4ecafd50 or 2d6b42a61373144298070668fddf06efe79cf2ff or ec7e62d77193131227df49d654d118fdf5a59892 or 5bbf0cd9b6a7076af86c75e87e180099be2e11ae, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux4c14a2fb5d143e4ed94143be2b8c1961b47df9af up to, but not including, f27ce82eb04960465df71634b196a48a4ecafd50; 4c14a2fb5d143e4ed94143be2b8c1961b47df9af up to, but not including, 2d6b42a61373144298070668fddf06efe79cf2ff; 4c14a2fb5d143e4ed94143be2b8c1961b47df9af up to, but not including, ec7e62d77193131227df49d654d118fdf5a59892; 4c14a2fb5d143e4ed94143be2b8c1961b47df9af up to, but not including, 5bbf0cd9b6a7076af86c75e87e180099be2e11ae; 4c14a2fb5d143e4ed94143be2b8c1961b47df9af up to, but not including, de80808f37d99c6dc67bb6f97eea00c8f57a8821; 4c14a2fb5d143e4ed94143be2b8c1961b47df9af up to, but not including, f20dedce0429b293d4bad604e0d3f65d8ac96c83; 4c14a2fb5d143e4ed94143be2b8c1961b47df9af up to, but not including, e09e0301d616c1ef38a5e64e8e4326fd39df13cc; 4c14a2fb5d143e4ed94143be2b8c1961b47df9af up to, but not including, fd3a3f28ed60c6af4b2a39933b151d6b27842c3b; and 1 more rangesf27ce82eb04960465df71634b196a48a4ecafd50, 2d6b42a61373144298070668fddf06efe79cf2ff, ec7e62d77193131227df49d654d118fdf5a59892, 5bbf0cd9b6a7076af86c75e87e180099be2e11ae, de80808f37d99c6dc67bb6f97eea00c8f57a8821, f20dedce0429b293d4bad604e0d3f65d8ac96c83

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
AdjacentThe attacker must be on the same local network segment.
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:A/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: mac802154: llsec: reject frames shorter than the authentication tag llsec_do_decrypt_auth() computes the associated-data length for the AEAD request as assoclen += datalen - authlen; where datalen is the number of bytes after the MAC header and authlen (4, 8 or 16) is the length of the authentication tag. Nothing verifies that the frame actually carries at least authlen payload bytes. A secured frame whose payload is shorter than the tag makes datalen - authlen negative; assoclen is then passed to aead_request_set_ad() as an unsigned value close to 4 GiB, so crypto_aead_decrypt() walks far off the end of the scatterlist that only spans the real frame. The frame is fully attacker-controlled and reaches this path from any IEEE 802.15.4 peer in radio range. Reject frames whose payload is shorter than the authentication tag before the subtraction. Dynamically reproduced on a KASAN kernel as a general-protection-fault in the AEAD scatterwalk, and the fix confirmed.

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.