Live › vulnerability › CVE-2026-115403
Eclipse ThreadX NetX Duo versions 6.0 through 6.5.2.202603a, built with BSD raw socket and IPv6 support, do not check whether a destination-table add succeeded. A remote sender who fills the table, for example with ICMPv6 Packet Too Big messages, can trigger a NULL pointer dereference that crashes the sending thread.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-02 22:35 UTC. All times on this page are UTC.
Devices running Eclipse ThreadX NetX Duo 6.0 through 6.5.2.202603a built with NX_BSD_RAW_SUPPORT and IPv6, whose app sends raw IPv6 packets with header inclusion to off-link destinations through a default router. The destination table can fill from the device's own traffic or from ICMPv6 Packet Too Big messages when path MTU discovery is on; the sending thread then crashes. Others can skip it.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| netxduo | vendor | >= 6.0, <= 6.5.2.202603a | 6.5.2.202603b |
Upgrade NetX Duo to 6.5.2.202603b
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In Eclipse ThreadX NetX Duo versions 6.0 through 6.5.2.202603a, built with BSD raw socket and IPv6 support, the IPv6 raw send path uses the destination-table entry it adds without checking that the add succeeded. When the destination table is full and an off-link destination is reached through a default router whose neighbour cache entry is unknown, sending on an IPv6 raw socket with header inclusion dereferences a NULL pointer; a remote sender can fill the table, for example with ICMPv6 Packet Too Big messages, and crash the sending thread.
This page as .md · .json · in your agent: get_signal("CVE-2026-115403")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.