NULL pointer dereference in the BSD raw IPv6 send path when the destination table is full
Affects Eclipse ThreadX 6.0 through 6.5.2.202603a in builds with NetX Duo raw IPv6 support. Fixed in NetX Duo 6.5.2.202603b.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 6.5.2.202603b
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 6.5.2.202603b.
- 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
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 6.5.2.202603b
- 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
Summary
Eclipse ThreadX NetX Duo, when built with BSD raw socket and IPv6 support, is affected. A remote sender can fill the destination table and crash the sending thread through a NULL pointer dereference, causing a denial of service.
Read the original description
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.
What to do
Upgrade to a fixed version: 6.5.2.202603b.
Workaround: Do not send raw IPv6 packets with IP_RAW_IPV6_HDRINCL to off-link destinations.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Eclipse Foundation Eclipse ThreadX
From 6.0 · through 6.5.2.202603a
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-115403
What does this mean?
A NULL pointer dereference in the BSD raw IPv6 send path crashes the thread that sends on the raw socket (SIGSEGV). On some targets, the word read at the faulting address may be used as the neighbour cache entry.Source: github.com
Am I affected, and how do I check?
The listed range is Eclipse ThreadX 6.0 through 6.5.2.202603a. The bug needs a build with NX_BSD_ENABLE, NX_BSD_RAW_SUPPORT and FEATURE_NX_IPV6, an application sending on an AF_INET6 raw socket with IP_RAW_IPV6_HDRINCL set, and an off-link destination that is not yet in the destination table while the table or neighbour cache is full. Check the version and these build settings to see how they compare with your setup.Source: github.com
What should I do about it?
Upgrade to NetX Duo 6.5.2.202603b, which contains the fix. Until the upgrade is applied, avoid sending raw IPv6 packets with IP_RAW_IPV6_HDRINCL to off-link destinations.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data