CVE-2025-40183High· 7.5▾ TwilightIn the Linux kernel, the following vulnerability has been resolved: bpf: Fix metadata_dst leak __bpf_redirect_neigh_v{4,6} Cilium has a BPF egress gateway feature which forces outgoing K8s Pod traffic to pass through dedicated egress g…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 41.3 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 15.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.6%
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix metadata_dst leak __bpf_redirect_neigh_v{4,6}
Cilium has a BPF egress gateway feature which forces outgoing K8s Pod traffic to pass through dedicated egress gateways which then SNAT the traffic in order to interact with stable IPs outside the cluster.
The traffic is directed to the gateway via vxlan tunnel in collect md mode. A recent BPF change utilized the bpf_redirect_neigh() helper to forward packets after the arrival and decap on vxlan, which turned out over time that the kmalloc-256 slab usage in kernel was ever-increasing.
The issue was that vxlan allocates the metadata_dst object and attaches it through a fake dst entry to the skb. The latter was never released though given bpf_redirect_neigh() was merely setting the new dst entry via skb_dst_set() without dropping an existing one first.
Linux >= b4ab31414970a7a03a5d55d75083f2c101a30592 < 3fba965a9aac0fa3cbd8138436a37af9ab466d79Linux >= b4ab31414970a7a03a5d55d75083f2c101a30592 < 057764172fcc6ee2ccb6c41351a55a9f054dc8fdLinux >= b4ab31414970a7a03a5d55d75083f2c101a30592 < 2e67c2037382abb56497bb9d7b7e10be04eb5598Linux >= b4ab31414970a7a03a5d55d75083f2c101a30592 < b6bfe44b6dbb14a31d86c475cdc9c7689534fb09Linux >= b4ab31414970a7a03a5d55d75083f2c101a30592 < f36a305d30f557306d87c787ddffe094ac5dac89Linux >= b4ab31414970a7a03a5d55d75083f2c101a30592 < 7404ce888a45eb7da0508b7cbbe6f2e95302eeb8Linux >= b4ab31414970a7a03a5d55d75083f2c101a30592 < 23f3770e1a53e6c7a553135011f547209e141e72Linux 5.10Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets