Skip to content

Conversation

@yjq91115
Copy link

Summary

After tcp_conn_list_unlock, conn might be released, so conn->timeout = true is moved to the lock protection scope. At the same time, a temporary variable is used to store dev to prevent conn from being released.

Impact

Severity: High
Type: Race condition / Use-After-Free
Affected scenario: High-concurrency TCP connection timeout handling, especially on multi-core systems where the timing window between unlock and access can be exploited by other CPU cores

Testing

none

…ing released after tcp_conn_list_unlock.

Change-Id: I6eb1e873c76666c9dcbaab33c3fe7719751529f8
Signed-off-by: yangjianqing <[email protected]>
@github-actions github-actions bot added Area: Networking Effects networking subsystem Size: XS The size of the change in this PR is very small labels Jan 29, 2026
Copy link
Contributor

@linguini1 linguini1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Testing is required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area: Networking Effects networking subsystem Size: XS The size of the change in this PR is very small

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants