CVE-2026-102760: Use After Free
When NetX Secure is built with NXSECUREKEYCLEAR, every TLS record sent on an active session is wiped after it has been handed to TCP. By then the TCP layer owns the packet chain and may already have released it to the packet pool. The wipe therefore writes zeros into packets that are free or in use by another thread, and when a reused packet's pointers no longer describe the old data, the length of the wipe underflows and it runs past the end of the packet pool.
Affected Software
Event History
Frequently Asked Questions
Which deployments are affected?
Deployments are affected when NetX Secure is built with NX_SECURE_KEY_CLEAR and an active TLS session sends TLS records. The provided data does not establish whether this build option is enabled by default.
How can I determine whether my build is exposed?
Review the NetX Secure build configuration and compiler definitions for NX_SECURE_KEY_CLEAR. If it is defined, TLS record transmission can trigger writes to packet chains after TCP has taken ownership of them.
What can be done if an update cannot be applied immediately?
Rebuild NetX Secure without NX_SECURE_KEY_CLEAR where operationally feasible. This removes the described post-handoff packet wiping path that can corrupt the packet pool.