CVE-2026-5590

net: ip/tcp: Null pointer dereference can be triggered by a race condition

Published Apr 5, 2026 CVSS 3.1 · 6.4 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

A race condition in the Zephyr TCP stack can cause the tcp_recv() routine to operate on a connection that has already been released. When tcp_conn_search() returns NULL during the processing of a SYN packet, a NULL pointer that originates from stale context data is passed to the function tcp_backlog_is_full() and dereferenced without validation. This unvalidated dereference results in a crash, terminating the Zephyr system or the affected process. The flaw aligns with CWE‑476, a null pointer dereference weakness. No escalation or data disclosure beyond the resulting crash is documented. The primary impact is a denial of service that can affect the availability of the embedded device or network service running Zephyr.

Affected Systems

The vulnerability is reported to affect the Zephyr operating system provided by zephyrproject‑rtos. No specific release or version range is specified in the available CNA data; system administrators must consult the linked advisory for detailed version guidance.

Risk and Exploitability

The CVSS base score of 6.4 indicates a moderate severity. EPSS data is not available, and the flaw is not listed in the CISA KEV catalog, implying no currently known exploited cases. The attack likely requires a precise race condition during TCP connection teardown, which may be triggered by a sequence of crafted network packets or concurrent traffic. Because the flaw is triggered internally within the Zephyr TCP stack, remote exploitation is not explicitly confirmed, but local or privileged users capable of creating such a race could force a crash. The overall risk is moderate, with the threat mainly being a denial of service to the target device.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest Zephyr patch that addresses the TCP teardown race condition.
  • If an immediate patch is unavailable, consider disabling the TCP stack or limiting concurrent connections to reduce the chance of a race condition.
  • Monitor the Zephyr project security advisories for updates and verify that the affected version is no longer present in the system.

Generated by OpenCVE AI on April 5, 2026 at 06:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Zephyrproject-rtos
Zephyrproject-rtos zephyr
Vendors & Products Zephyrproject-rtos
Zephyrproject-rtos zephyr
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title net: ip/tcp: Null pointer dereference can be triggered by a race condition
Weaknesses CWE-476
References
Metrics cvssV3_1

{'score': 6.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
zephyr
Published
Updated
Oct 15, 2026, 10:10 PM
Reserved
Apr 5, 2026, 3:23 AM
Status
Analyzed
Published
Apr 5, 2026, 4:16 AM
Modified
Oct 15, 2026, 11:17 PM