CVE-2026-90106 json
net: bridge: arp/nd proxy: fix reading neigh ha
published 2026-09-17 52 d ago modified 2026-10-30 9 d ago also EUVD-2026-81699
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 13%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
net: bridge: arp/nd proxy: fix reading neigh ha
Currently neigh ha address is read directly, but that can result in torn/partial reads if the neigh is being updated. Use neigh_ha_snapshot to take a stable snapshot of the address.
Patch / fix
- Linux Linux 6.1.191, 6.6.160, 6.12.114, 6.18.57, 7.2.6, 7.3
- linux Debian 13 6.12.115-2
- linux Debian 14 7.2.6-1
debian advisories DEBIAN-CVE-2026-90106
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-ibm Ubuntu 26.04 LTS 7.0.0-1017.17
- linux-riscv Ubuntu 26.04 LTS 7.0.0-42.42.1
- linux-oracle Ubuntu 26.04 LTS 7.0.0-1015.16
- linux-hwe-7.0 Ubuntu 24.04 LTS 7.0.0-42.42~24.04.1
- linux-oem-7.0 Ubuntu 26.04 LTS 7.0.0-1017.17
ubuntu advisories UBUNTU-CVE-2026-90106
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source openSUSE Tumbleweed 7.2.7-1.1
opensuse advisories openSUSE-SU-2026:11880-1
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-102432
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/2365b25b4add42bb5f652920b45bc9ad0e35cbc7 commit
- git.kernel.org/stable/c/490c72868443ff90f47f4ccbaaff1eaf8fed46ab commit
- git.kernel.org/stable/c/a178bcb01051688fb085ffb72cc4b13b5df0fc0f commit
- git.kernel.org/stable/c/884cbf15ccd3980bcc9583073045f91798a86d4e commit
- git.kernel.org/stable/c/291c9e137b7c74e8a512cded4845352da4c4adda commit
- git.kernel.org/stable/c/57549ab9079122991dfa0f8248ca00e101e8e69b commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-90106 updated cvss 5.5
kernel: net: bridge: arp/nd proxy: fix reading neigh ha
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: workaround, no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/2365b25b4add42bb5f652920b45bc9ad0e35cbc7
- git.kernel.org /stable/c/490c72868443ff90f47f4ccbaaff1eaf8fed46ab
- git.kernel.org /stable/c/a178bcb01051688fb085ffb72cc4b13b5df0fc0f
- git.kernel.org /stable/c/884cbf15ccd3980bcc9583073045f91798a86d4e
- git.kernel.org /stable/c/291c9e137b7c74e8a512cded4845352da4c4adda
- git.kernel.org /stable/c/57549ab9079122991dfa0f8248ca00e101e8e69b
Sources
- CVE List CVE-2026-90106
- NVD CVE-2026-90106
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.