CyberSecBulletin
CVE-2026-46039NVD status: Analyzed

Linux: Integer Overflow or Wraparound

Published Updated By the CyberSecBulletin desk

CVE-2026-46039 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 43222ac484f93b3ec2d240a7575e1cedd31f5fa4, 183d37f12d1c8ed24a5bfc7addad05510da22a94, 6929350080f4da292d111a3b33e53138fee51cec 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.44% chance of exploitation within 30 days, which is low compared with other CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update Linux to 43222ac484f93b3ec2d240a7575e1cedd31f5fa4 or 183d37f12d1c8ed24a5bfc7addad05510da22a94 or 6929350080f4da292d111a3b33e53138fee51cec or 6.17, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.17 or 6.18.27 or 7.0.4, whichever matches your release line, or a later version.
  3. 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
LinuxLinux2429a197648178cd4dc930a9d87c13c547460564 up to, but not including, 43222ac484f93b3ec2d240a7575e1cedd31f5fa4; 2429a197648178cd4dc930a9d87c13c547460564 up to, but not including, 183d37f12d1c8ed24a5bfc7addad05510da22a94; 2429a197648178cd4dc930a9d87c13c547460564 up to, but not including, 6929350080f4da292d111a3b33e53138fee51cec; 71571e187106631a8127f2dde780f35caa358d33; 6.16.9 up to, but not including, 6.17; 6.1743222ac484f93b3ec2d240a7575e1cedd31f5fa4, 183d37f12d1c8ed24a5bfc7addad05510da22a94, 6929350080f4da292d111a3b33e53138fee51cec, 6.17
LinuxLinux Kernel6.16.9 up to, but not including, 6.17; 6.17.1 up to, but not including, 6.18.27; 6.19 up to, but not including, 7.0.4; 6.176.17, 6.18.27, 7.0.4

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: rxgk: Fix potential integer overflow in length check Fix potential integer overflow in rxgk_extract_token() when checking the length of the ticket. Rather than rounding up the value to be tested (which might overflow), round down the size of the available data.

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.