CVE-2024-35839: netfilter: bridge: replace physindev with physinif in nf_bridge_info
First published: Fri May 17 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: netfilter: bridge: replace physindev with physinif in nf_bridge_info An skb can be added to a neigh->arp_queue while waiting for an arp reply. Where original skb's skb->dev can be different to neigh's neigh->dev. For instance in case of bridging dnated skb from one veth to another, the skb would be added to a neigh->arp_queue of the bridge. As skb->dev can be reset back to nf_bridge->physindev and used, and as there is no explicit mechanism that prevents this physindev from been freed under us (for instance neigh_flush_dev doesn't cleanup skbs from different device's neigh queue) we can crash on e.g. this stack: arp_process neigh_update skb = __skb_dequeue(&neigh->arp_queue) neigh_resolve_output(..., skb) ... br_nf_dev_xmit br_nf_pre_routing_finish_bridge_slow skb->dev = nf_bridge->physindev br_handle_frame_finish Let's use plain ifindex instead of net_device link. To peek into the original net_device we will use dev_get_by_index_rcu(). Thus either we get device and are safe to use it or we don't get it and drop skb.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/kernel | <6.1.75 | 6.1.75 |
| redhat/kernel | <6.6.14 | 6.6.14 |
| redhat/kernel | <6.7.2 | 6.7.2 |
| redhat/kernel | <6.8 | 6.8 |
| debian/linux | <=5.10.223-1<=5.10.226-1 | 6.1.123-1 6.1.119-1 6.12.11-1 6.12.12-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/544add1f1cfb78c3dfa3e6edcf4668f6be5e730c
- https://git.kernel.org/stable/c/7ae19ee81ca56b13c50a78de6c47d5b8fdc9d97b
- https://git.kernel.org/stable/c/9325e3188a9cf3f69fc6f32af59844bbc5b90547
- https://git.kernel.org/stable/c/9874808878d9eed407e3977fd11fee49de1e1d86
- https://launchpad.net/bugs/cve/CVE-2024-35839
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-35839
- https://nvd.nist.gov/vuln/detail/CVE-2024-35839
- https://security-tracker.debian.org/tracker/CVE-2024-35839
- https://ubuntu.com/security/CVE-2024-35839
- https://access.redhat.com/security/cve/CVE-2024-35839
- https://lore.kernel.org/linux-cve-announce/2024051756-CVE-2024-35839-4194@gregkh/T
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2281285
- https://access.redhat.com/errata/RHSA-2024:5928
- https://access.redhat.com/errata/RHSA-2024:6268
- https://access.redhat.com/errata/RHSA-2024:6267
- https://access.redhat.com/errata/RHSA-2024:8870
- https://access.redhat.com/errata/RHSA-2024:8856
- https://bugzilla.redhat.com/show_bug.cgi?id=2281284
- https://git.kernel.org/linus/9874808878d9eed407e3977fd11fee49de1e1d86
- agent/type
- agent/title
- collector/nvd-api
- source/NVD
- collector/epss-latest
- source/FIRST
- agent/epss
- agent/remedy
- agent/first-publish-date
- collector/launchpad-cve
- source/Launchpad
- agent/author
- collector/usn-cve
- source/Ubuntu
- agent/event
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2024-35839
- agent/software-canonical-lookup
- collector/nvd-cve
- collector/mitre-cve
- source/MITRE
- agent/description
- agent/severity
- agent/last-modified-date
- agent/references
- agent/trending
- agent/source
- agent/tags
- agent/softwarecombine
- collector/security-tracker-debian
- source/Debian
- package-manager/redhat
- package-manager/debian