CVE-2026-10636: use-after-free in zephyrproject zephyr
In Zephyr's IPv4 IGMP implementation, igmp_send() in subsys/net/ip/igmp.c read the network interface back out of the packet via net_pkt_iface(pkt) after the packet had been handed to net_send_data(). On the successful-send path the packet's last reference may already have been released by the L2 driver or by the network stack's TX handling (synchronously in the default NET_TC_TX_COUNT=0 immediate-transmit configuration), returning the net_pkt slab block to its free list. The subsequent net_pkt_iface(pkt) dereferences the freed packet, a use-after-free read; with CONFIG_NET_STATISTICS_PER_INTERFACE the resulting dangling interface pointer is further dereferenced for a statistics-counter write. The IGMP send path is reachable without authentication from inbound IPv4 IGMP membership queries addressed to 224.0.0.1 (net_ipv4_igmp_input -> send_igmp_report/send_igmp_v3_report -> igmp_send), as well as from local multicast join/leave/rejoin operations. Realistic impact is undefined behavior and potential denial of service (sporadic crash or stats corruption); a controllable write requires the asynchronous TX path plus a concurrent slab reuse. The flaw was introduced with IGMPv2 support and affects releases from v2.6.0 through v4.4.0. The fix caches the interface pointer before sending. Note the analogous IPv6 MLD path (mld_send in subsys/net/ip/ipv6_mld.c) retains the same unfixed pattern.
AI Analysis
Technical Summary
In Zephyr's IPv4 IGMP implementation, the igmp_send() function reads the network interface pointer from a packet after the packet has been passed to net_send_data(). On successful send, the packet's last reference may be released, freeing the memory. Subsequent access to the freed packet leads to a use-after-free read. If CONFIG_NET_STATISTICS_PER_INTERFACE is enabled, the dangling pointer is further dereferenced for statistics updates. This flaw is reachable without authentication via inbound IGMP membership queries to 224.0.0.1 and local multicast join/leave operations. The vulnerability affects Zephyr versions from 2.6.0 through 4.4.0 and was introduced with IGMPv2 support. The fix involves caching the interface pointer before sending. The similar IPv6 MLD send path remains vulnerable.
Potential Impact
The vulnerability can cause undefined behavior including sporadic crashes or corruption of network statistics counters, resulting in potential denial of service. There is no confidentiality or integrity impact. Exploitation requires triggering the asynchronous TX path and concurrent slab reuse, making controlled writes unlikely. No known exploits are reported in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The fix involves caching the interface pointer before sending the packet. Until an official fix is available, avoid configurations that enable asynchronous TX paths or CONFIG_NET_STATISTICS_PER_INTERFACE if feasible. Monitor vendor communications for updates and apply patches once released.
CVE-2026-10636: use-after-free in zephyrproject zephyr
Description
In Zephyr's IPv4 IGMP implementation, igmp_send() in subsys/net/ip/igmp.c read the network interface back out of the packet via net_pkt_iface(pkt) after the packet had been handed to net_send_data(). On the successful-send path the packet's last reference may already have been released by the L2 driver or by the network stack's TX handling (synchronously in the default NET_TC_TX_COUNT=0 immediate-transmit configuration), returning the net_pkt slab block to its free list. The subsequent net_pkt_iface(pkt) dereferences the freed packet, a use-after-free read; with CONFIG_NET_STATISTICS_PER_INTERFACE the resulting dangling interface pointer is further dereferenced for a statistics-counter write. The IGMP send path is reachable without authentication from inbound IPv4 IGMP membership queries addressed to 224.0.0.1 (net_ipv4_igmp_input -> send_igmp_report/send_igmp_v3_report -> igmp_send), as well as from local multicast join/leave/rejoin operations. Realistic impact is undefined behavior and potential denial of service (sporadic crash or stats corruption); a controllable write requires the asynchronous TX path plus a concurrent slab reuse. The flaw was introduced with IGMPv2 support and affects releases from v2.6.0 through v4.4.0. The fix caches the interface pointer before sending. Note the analogous IPv6 MLD path (mld_send in subsys/net/ip/ipv6_mld.c) retains the same unfixed pattern.
CVSS v3.1
Score 3.7low
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In Zephyr's IPv4 IGMP implementation, the igmp_send() function reads the network interface pointer from a packet after the packet has been passed to net_send_data(). On successful send, the packet's last reference may be released, freeing the memory. Subsequent access to the freed packet leads to a use-after-free read. If CONFIG_NET_STATISTICS_PER_INTERFACE is enabled, the dangling pointer is further dereferenced for statistics updates. This flaw is reachable without authentication via inbound IGMP membership queries to 224.0.0.1 and local multicast join/leave operations. The vulnerability affects Zephyr versions from 2.6.0 through 4.4.0 and was introduced with IGMPv2 support. The fix involves caching the interface pointer before sending. The similar IPv6 MLD send path remains vulnerable.
Potential Impact
The vulnerability can cause undefined behavior including sporadic crashes or corruption of network statistics counters, resulting in potential denial of service. There is no confidentiality or integrity impact. Exploitation requires triggering the asynchronous TX path and concurrent slab reuse, making controlled writes unlikely. No known exploits are reported in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The fix involves caching the interface pointer before sending the packet. Until an official fix is available, avoid configurations that enable asynchronous TX paths or CONFIG_NET_STATISTICS_PER_INTERFACE if feasible. Monitor vendor communications for updates and apply patches once released.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- zephyr
- Date Reserved
- 2026-06-02T15:10:53.319Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3165080b89be6888c91b1b
Added to database: 06/16/2026, 15:00:24 UTC
Last enriched: 07/15/2026, 10:45:04 UTC
Last updated: 07/31/2026, 19:22:57 UTC
Views: 72
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.