CyberSecBulletin
CVE-2026-46043NVD status: Modified

Linux: Integer Overflow or Wraparound

Published Updated By the CyberSecBulletin desk

CVE-2026-46043 is a critical-severity integer overflow or wraparound vulnerability in Linux, with a CVSS 3.1 base score of 9.1 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 c4376c672c3648d5bdc31dfffc329d07164f93c4, 5fedefec757192dcaad29a664ac332c7601be144, 2c0d71ef12f46c57d37bc571f3f2797db7eb50cc 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.51% 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 c4376c672c3648d5bdc31dfffc329d07164f93c4 or 5fedefec757192dcaad29a664ac332c7601be144 or 2c0d71ef12f46c57d37bc571f3f2797db7eb50cc or 2fd4f8b749309a61c3f3f88ee8891d94f79e1240, 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.140, 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
LinuxLinux8700e3e7c4857d28ebaa824509934556da0b3e76 up to, but not including, c4376c672c3648d5bdc31dfffc329d07164f93c4; 8700e3e7c4857d28ebaa824509934556da0b3e76 up to, but not including, 5fedefec757192dcaad29a664ac332c7601be144; 8700e3e7c4857d28ebaa824509934556da0b3e76 up to, but not including, 2c0d71ef12f46c57d37bc571f3f2797db7eb50cc; 8700e3e7c4857d28ebaa824509934556da0b3e76 up to, but not including, 2fd4f8b749309a61c3f3f88ee8891d94f79e1240; 8700e3e7c4857d28ebaa824509934556da0b3e76 up to, but not including, f83519a4c122c9c7a850a2197648a9ff4c67c520; 8700e3e7c4857d28ebaa824509934556da0b3e76 up to, but not including, 9b924f3a26b21330a837cfe72e819b6393bbeeaa; 8700e3e7c4857d28ebaa824509934556da0b3e76 up to, but not including, e8ee0e792d475b1067c199ef0af1b6221fa6f43d; 8700e3e7c4857d28ebaa824509934556da0b3e76 up to, but not including, 7244491dab347f648e661da96dc0febadd9daec3; and 1 more rangesc4376c672c3648d5bdc31dfffc329d07164f93c4, 5fedefec757192dcaad29a664ac332c7601be144, 2c0d71ef12f46c57d37bc571f3f2797db7eb50cc, 2fd4f8b749309a61c3f3f88ee8891d94f79e1240, f83519a4c122c9c7a850a2197648a9ff4c67c520, 9b924f3a26b21330a837cfe72e819b6393bbeeaa
LinuxLinux Kernel4.8 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.140; 6.7 up to, but not including, 6.12.86; 6.13 up to, but not including, 6.18.27; 6.19 up to, but not including, 7.0.45.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.86, 6.18.27

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

Official description

In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Validate pad and ICRC before payload_size() in rxe_rcv rxe_rcv() currently checks only that the incoming packet is at least header_size(pkt) bytes long before payload_size() is used. However, payload_size() subtracts both the attacker-controlled BTH pad field and RXE_ICRC_SIZE from pkt->paylen: payload_size = pkt->paylen - offset[RXE_PAYLOAD] - bth_pad(pkt) - RXE_ICRC_SIZE This means a short packet can still make payload_size() underflow even if it includes enough bytes for the fixed headers. Simply requiring header_size(pkt) + RXE_ICRC_SIZE is not sufficient either, because a packet with a forged non-zero BTH pad can still leave payload_size() negative and pass an underflowed value to later receive-path users. Fix this by validating pkt->paylen against the full minimum length required by payload_size(): header_size(pkt) + bth_pad(pkt) + RXE_ICRC_SIZE.

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

References

Recent Integer Overflow or Wraparound vulnerabilities

Spotted an error? Tell us.