# CVE-2026-46037: ipv4: icmp: validate reply type before using icmp_pointers

> A missing bounds check in the Linux kernel's ICMP handling allows out-of-bounds memory reads, potentially leading to information disclosure or system crashes.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 May 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-88671, BELL-CVE-2026-46037, DEBIAN-CVE-2026-46037, GHSA-hxj2-jf3v-xp24, ROOT-OS-DEBIAN-12-CVE-2026-46037, ROOT-OS-UBUNTU-2204-CVE-2026-46037, ROOT-OS-UBUNTU-2404-CVE-2026-46037, UBUNTU-CVE-2026-46037

## What is CVE-2026-46037?

CVE-2026-46037 is a high-severity memory corruption vulnerability in Linux kernel, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-46037?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-46037?

Apply the vendor's patch.

## Is CVE-2026-46037 being exploited?

There is no known exploitation of CVE-2026-46037 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46037 and fix it if it is affected.

What it is: CVE-2026-46037 is a high-severity memory corruption vulnerability in Linux kernel, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46037 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46037/ (Markdown: https://insights.sbomify.com/CVE-2026-46037/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46037
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46037
- OSV: https://osv.dev/vulnerability/CVE-2026-46037

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46037/
Summaries are generated and may contain mistakes; the official description above is the record.