# CVE-2026-64413: netfilter: ebtables: zero chainstack array

> A potential null pointer dereference in the Linux kernel ebtables module could cause a denial of service if memory allocation fails during initialization.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jul 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-93930, BELL-CVE-2026-64413, DEBIAN-CVE-2026-64413, GHSA-48r8-x424-wvc7, ROOT-OS-DEBIAN-12-CVE-2026-64413, ROOT-OS-DEBIAN-13-CVE-2026-64413, ROOT-OS-UBUNTU-2204-CVE-2026-64413, UBUNTU-CVE-2026-64413

## What is CVE-2026-64413?

CVE-2026-64413 is a high-severity vulnerability in Linux kernel, published on 25 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

netfilter: ebtables: zero chainstack array

sashiko reports:
 looking at ebtables table
 translation, could a sparse cpu_possible_mask lead to an uninitialized pointer
 free?

 If cpu_possible_mask is sparse (for example, CPU 0 and CPU 2 are possible,
 but CPU 1 is not), the allocation loop skips CPU 1. If vmalloc_node() fails at
 CPU 2, the cleanup loop will blindly decrement and call vfree() on
 newinfo->chainstack[1].

Not a real-world bug, such allocation isn't expected to fail
in the first place.

Weakness: CWE-908 (Use of Uninitialized Resource), CWE-457 (Use of Uninitialized Variable)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2026-64413 being exploited?

There is no known exploitation of CVE-2026-64413 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-64413 and fix it if it is affected.

What it is: CVE-2026-64413 is a high-severity vulnerability in Linux kernel, published on 25 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-64413 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-64413/ (Markdown: https://insights.sbomify.com/CVE-2026-64413/index.md)
```

## Sources

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

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