GHSA-8rp9-5755-q75w: NULL pointer dereference when evicting the last MSRP attribute in a participant’s list

GHSA ID

GHSA‑8rp9‑5755‑q75w

CVE ID

CVE‑2026‑102724

Severity

High

CWE

CWE-476

Published

2026‑11‑01

Last updated

2026‑11‑01

Affected packages

Package Vulnerable versions Patched versions

NetX Duo

>= 6.4.0, ⇐ 6.5.2.202603a

6.5.2.202603b

Description

Summary

When the NetX Duo MRP implementation evicts an attribute that is the last entry in a participant’s list, nx_mrp_attribute_evict() writes through the null successor pointer and faults the MRP worker thread. An unauthenticated station on the same Layer 2 segment can trigger this by declaring one MSRP attribute and withdrawing it; ordinary withdrawals by legitimate talkers and listeners reach the same path whenever the evicted attribute is last in the list.

Details

nx_mrp_attribute_evict() unlinks an attribute from the participant’s doubly linked list once its registrar is empty and its applicant is in an observer state. Both branches of the unlink write attribute → next → pre without checking that next exists: the branch for a head entry clears it, and the branch for any other entry copies the predecessor into it. For the last entry in the list, next is NX_NULL, so either branch writes through a null pointer.

The path is reached from the network. A declaration (New) moves the registrar to IN; a withdrawal (Leave) moves it to LV and starts the leave timer; join-timer processing moves the applicant to an observer state; and when the leave timer expires, nx_mrp_leave_timeout_process() calls nx_mrp_attribute_evict(). A single attribute declared and withdrawn by an attacker is both head and tail of the list, which is the simplest case, but any tail entry faults the same way.

Impact

An unauthenticated station on the same Layer 2 segment faults the MRP worker thread about a second after withdrawing its declaration, which on most targets stops MSRP processing or resets the device. The faulting access is a pointer-sized write at a low address; on a target whose memory map places writable memory at address zero it corrupts that memory instead of faulting. Because legitimate withdrawals reach the same code, affected devices can also fail in normal operation. No confidentiality impact has been identified.

Affected configurations

Applications built with NX_ENABLE_VLAN that initialize SRP with nx_srp_init(). MRP traffic is not routed, so the attacker must be on the same Layer 2 segment or VLAN.

Affected versions: [6.4.0, 6.5.2.202603a]. 6.4.0 introduced the TSN components.

Severity

CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N, CVSS-B 7.1 (High). CWE-476: NULL Pointer Dereference.

The leave timer is part of the protocol and runs to expiry without any race, so no attack requirement is scored; the configuration requirement is stated above.

Patches

Fixed in NetX Duo 6.5.2.202603b. nx_mrp_attribute_evict() now finds the predecessor by walking the participant’s list from its head, updates the successor’s link only when there is a successor, and leaves an attribute that is not in the list untouched. This differs from the unlink first planned, which relied on the predecessor links: MSRP never sets them, so evicting a middle MSRP attribute also dropped every attribute before it from the list, which the fix corrects as well. A new regression test expires the leave timers of the only, first, middle and last of three MSRP attributes, and of combinations of them; it faults without the fix.

Credits

Found by SecMate automated analysis (https://secmate.dev/). Reported by VulnCheck. Fixed by Frédéric Desbiens.

The fix and regression test were produced with AI assistance under human review, in accordance with the Eclipse Foundation’s Generative AI Usage Guidelines.