bpf: Fix metadata_dst leak __bpf_redirect_neigh_v{4,6}
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.246, 5.15.195, 6.1.157, 6.6.113, 6.12.54, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From b4ab31414970a7a03a5d55d75083f2c101a30592 · fixed in 3fba965a9aac0fa3cbd8138436a37af9ab466d79; From b4ab31414970a7a03a5d55d75083f2c101a30592 · fixed in 057764172fcc6ee2ccb6c41351a55a9f054dc8fd; From b4ab31414970a7a03a5d55d75083f2c101a30592 · fixed in 2e67c2037382abb56497bb9d7b7e10be04eb5598; From b4ab31414970a7a03a5d55d75083f2c101a30592 · fixed in b6bfe44b6dbb14a31d86c475cdc9c7689534fb09; From b4ab31414970a7a03a5d55d75083f2c101a30592 · fixed in f36a305d30f557306d87c787ddffe094ac5dac89; From b4ab31414970a7a03a5d55d75083f2c101a30592 · fixed in 7404ce888a45eb7da0508b7cbbe6f2e95302eeb8; From b4ab31414970a7a03a5d55d75083f2c101a30592 · fixed in 23f3770e1a53e6c7a553135011f547209e141e72
- Linux Linux
5.10
- KernelLinux
From 5.10.0 · fixed in 5.10.246; From 5.11.0 · fixed in 5.15.195; From 5.16.0 · fixed in 6.1.157; From 6.2.0 · fixed in 6.6.113; From 6.7.0 · fixed in 6.12.54; From 6.13.0 · fixed in 6.17.4
References 7
git.kernel.org
- stable/c/3fba965a9aac0fa3cbd8138436a37af9ab466d79
- stable/c/057764172fcc6ee2ccb6c41351a55a9f054dc8fd
- stable/c/2e67c2037382abb56497bb9d7b7e10be04eb5598
- stable/c/b6bfe44b6dbb14a31d86c475cdc9c7689534fb09
- stable/c/f36a305d30f557306d87c787ddffe094ac5dac89
- stable/c/7404ce888a45eb7da0508b7cbbe6f2e95302eeb8
- stable/c/23f3770e1a53e6c7a553135011f547209e141e72