PatchSiren cyber security CVE debrief
CVE-2026-5590 zephyrproject-rtos CVE debrief
A race condition during TCP connection teardown can cause tcp_recv() to operate on a connection that has already been released. If tcp_conn_search() returns NULL while processing a SYN packet, a NULL pointer derived from stale context data is passed to tcp_backlog_is_full() and dereferenced without validation, leading to a crash. This vulnerability affects users of the Zephyr project, particularly those using versions up to 4.3.0. The Common Vulnerability Scoring System (CVSS) score for this vulnerability is 6.4, indicating a medium severity.
- Vendor
- zephyrproject-rtos
- Product
- Zephyr
- CVSS
- MEDIUM 6.4
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-04-05
- Original CVE updated
- 2026-07-08
- Advisory published
- 2026-04-05
- Advisory updated
- 2026-07-08
Who should care
Users of Zephyr project Zephyr versions up to 4.3.0 should be aware of this vulnerability and take steps to mitigate it. This includes reviewing and updating inventory of affected systems, monitoring for potential exploitation attempts, and applying patches from the vendor.
Technical summary
The vulnerability is caused by a race condition during TCP connection teardown. When tcp_conn_search() returns NULL while processing a SYN packet, a NULL pointer derived from stale context data is passed to tcp_backlog_is_full() and dereferenced without validation, leading to a crash. The vulnerability affects the Zephyr project, specifically versions up to 4.3.0. Users of these versions should be aware of this vulnerability and take steps to mitigate it.
Defensive priority
Medium priority should be given to patching this vulnerability, as it can cause a crash and potentially be used by attackers.
Recommended defensive actions
- Apply the patch from the vendor
- Review and update inventory of affected systems
- Monitor for potential exploitation attempts
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record was published on 2026-04-05T04:16:16.370Z and was last modified on 2026-07-08T13:38:21.667Z. The NVD entry is currently Analyzed. This information is based on the provided source corpus. Further verification is recommended to ensure accuracy.
Official resources
-
CVE-2026-5590 CVE record
CVE.org
-
CVE-2026-5590 NVD detail
NVD
-
Source item URL
nvd_modified
-
Mitigation or vendor reference
[email protected] - Exploit, Patch, Vendor Advisory
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-04-05T04:16:16.370Z and has not been modified since then. The NVD entry is currently Analyzed.