Skip to main content
VulnerabilityPublished Updated

CVE-2026-46037: Linux kernel · ipv4: icmp: validate reply type before using icmp_pointers

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 8.2 High · fixed in d700c34a5d186b9ba0715bcb19e0ff80ffbfbfc1 : patch Linux kernel soon.

Data as of 26 Oct 2026, 13:07 UTC

CVSS 3.1 base score
8.2High
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 d700c34a5d186b9ba0715bcb19e0ff80ffbfbfc1, c2178ff1c70ebfc2ab9651b230c58a34683db759, bc64a66e0b9ad937d3d49934242ee62b01ba9a94 +4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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
  • ≥ d329ea5bd8845f0b196bf41b18b6173340d6e0e4, < d700c34a5d186b9ba0715bcb19e0ff80ffbfbfc1
Fixed in
  • d700c34a5d186b9ba0715bcb19e0ff80ffbfbfc1
LinuxLinuxAffected
  • ≥ d329ea5bd8845f0b196bf41b18b6173340d6e0e4, < c2178ff1c70ebfc2ab9651b230c58a34683db759
Fixed in
  • c2178ff1c70ebfc2ab9651b230c58a34683db759
LinuxLinuxAffected
  • ≥ d329ea5bd8845f0b196bf41b18b6173340d6e0e4, < bc64a66e0b9ad937d3d49934242ee62b01ba9a94
Fixed in
  • bc64a66e0b9ad937d3d49934242ee62b01ba9a94
LinuxLinuxAffected
  • ≥ d329ea5bd8845f0b196bf41b18b6173340d6e0e4, < b3a88fc5ae024d43c5ecf653f3bbe837e4a6dc99
Fixed in
  • b3a88fc5ae024d43c5ecf653f3bbe837e4a6dc99
LinuxLinuxAffected
  • ≥ d329ea5bd8845f0b196bf41b18b6173340d6e0e4, < 93df2af4f491de33827550b9d420f01808c0706b
Fixed in
  • 93df2af4f491de33827550b9d420f01808c0706b
LinuxLinuxAffected
  • ≥ d329ea5bd8845f0b196bf41b18b6173340d6e0e4, < 92e7c209036dcc0e8ffdf806fdfd3645b263bea5
Fixed in
  • 92e7c209036dcc0e8ffdf806fdfd3645b263bea5

Description

In the Linux kernel, the following vulnerability has been resolved: ipv4: icmp: validate reply type before using icmp_pointers Extended echo replies use ICMP_EXT_ECHOREPLY as the outbound reply type. That value is outside the range covered by icmp_pointers[], which only describes the traditional ICMP types up to NR_ICMP_TYPES. Avoid consulting icmp_pointers[] for reply types outside that range, and use array_index_nospec() for the remaining in-range lookup. Normal ICMP replies keep their existing behavior unchanged.

References

Community reviews

Loading reviews…