Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

net: tcp.c: prepare_segment() may leak fragments in case of error #4323

Closed
pfalcon opened this issue Oct 14, 2017 · 4 comments
Closed

net: tcp.c: prepare_segment() may leak fragments in case of error #4323

pfalcon opened this issue Oct 14, 2017 · 4 comments
Assignees
Labels
area: Networking bug The issue is a bug, or the PR is fixing a bug priority: high High impact/importance bug

Comments

@pfalcon
Copy link
Contributor

pfalcon commented Oct 14, 2017

Continuing from #4292 (comment) :

prepare_segment() has code like: https://github.com/zephyrproject-rtos/zephyr/blob/master/subsys/net/ip/tcp.c#L346 , which means that in case of early error return (e.g. https://github.com/zephyrproject-rtos/zephyr/blob/master/subsys/net/ip/tcp.c#L384), the original fragment chain of incoming packet will be lost and leaked.

@pfalcon pfalcon added area: Networking priority: high High impact/importance bug labels Oct 14, 2017
@nashif nashif added the bug The issue is a bug, or the PR is fixing a bug label Oct 14, 2017
@jukkar
Copy link
Member

jukkar commented Oct 27, 2017

Is there still some issue with this, I thought this was fixed by #4292 or is the bug description wrong.

@pfalcon
Copy link
Contributor Author

pfalcon commented Oct 27, 2017

No, this wasn't fixed by #4292, this is a separate issue, and the title and description are correct.

I'd say, this waits triaging by the maintainers, to confirm the issue and priority of "high".

@linkmeyer
Copy link

@jukkar , @tbursztyka , what's the status?

@jukkar
Copy link
Member

jukkar commented Nov 14, 2017

The #4907 looks like a perfect match that would fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Networking bug The issue is a bug, or the PR is fixing a bug priority: high High impact/importance bug
Projects
None yet
Development

No branches or pull requests

5 participants