Skip to main content
VulnerabilityPublished Updated

CVE-2026-46043: Linux kernel · Integer Overflow

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical · fixed in f83519a4c122c9c7a850a2197648a9ff4c67c520 : patch Linux kernel as a priority.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in f83519a4c122c9c7a850a2197648a9ff4c67c520, e8ee0e792d475b1067c199ef0af1b6221fa6f43d, c4376c672c3648d5bdc31dfffc329d07164f93c4 +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 8700e3e7c4857d28ebaa824509934556da0b3e76, < f83519a4c122c9c7a850a2197648a9ff4c67c520
Fixed in
  • f83519a4c122c9c7a850a2197648a9ff4c67c520
LinuxLinuxAffected
  • ≥ 8700e3e7c4857d28ebaa824509934556da0b3e76, < e8ee0e792d475b1067c199ef0af1b6221fa6f43d
Fixed in
  • e8ee0e792d475b1067c199ef0af1b6221fa6f43d
LinuxLinuxAffected
  • ≥ 8700e3e7c4857d28ebaa824509934556da0b3e76, < c4376c672c3648d5bdc31dfffc329d07164f93c4
Fixed in
  • c4376c672c3648d5bdc31dfffc329d07164f93c4
LinuxLinuxAffected
  • ≥ 8700e3e7c4857d28ebaa824509934556da0b3e76, < 7244491dab347f648e661da96dc0febadd9daec3
Fixed in
  • 7244491dab347f648e661da96dc0febadd9daec3
LinuxLinuxAffected
  • ≥ 8700e3e7c4857d28ebaa824509934556da0b3e76, < 9b924f3a26b21330a837cfe72e819b6393bbeeaa
Fixed in
  • 9b924f3a26b21330a837cfe72e819b6393bbeeaa
LinuxLinuxAffected
  • ≥ 8700e3e7c4857d28ebaa824509934556da0b3e76, < 5fedefec757192dcaad29a664ac332c7601be144
Fixed in
  • 5fedefec757192dcaad29a664ac332c7601be144

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.

References

Community reviews

Loading reviews…