CVE-2024-35839
Last modified
CVE-2024-35839 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.22% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 4.2, < 6.1.75 |
| Linux | Linux Kernel | >= 6.2, < 6.6.14 |
| Linux | Linux Kernel | >= 6.7, < 6.7.2 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-35839?
How severe is CVE-2024-35839?
How do I fix CVE-2024-35839?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-35833In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-35834In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-35835In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-35836In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-35837In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-35838In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-3584qdrant/qdrant version 1.9.0-dev is vulnerable to path traver…7.5
- CVE-2024-35840In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-35841In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-35842In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-35843In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2024-35844In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2024-35839?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
