# CVE-2026-90105: vxlan: fix reading neigh ha

> A race condition in the Linux kernel VXLAN module allows partial reads of neighbor hardware addresses, potentially leading to data corruption or denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-103050, BELL-CVE-2026-90105, DEBIAN-CVE-2026-90105, GHSA-6mp3-g7qw-8rgw, UBUNTU-CVE-2026-90105

## What is CVE-2026-90105?

CVE-2026-90105 is a vulnerability in Linux, published on 17 Sep 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:

vxlan: fix reading neigh ha

Currently arp/neigh_reduce read neigh ha directly which can lead to
partial reads while the neigh is being updated. Use neigh_ha_snapshot to
take a stable snapshot of the address similar to route_shortcircuit which
already does the right thing.

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


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

Apply the vendor's patch.

## Is CVE-2026-90105 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90105 is a vulnerability in Linux, published on 17 Sep 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-90105 in the wild and no public exploit code.

Affected product: Linux. 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-90105/ (Markdown: https://insights.sbomify.com/CVE-2026-90105/index.md)
```

## Sources

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

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