Bug 1205258 - Busy loop in recv(MSG_PEEK|MSG_WAITALL)
Summary: Busy loop in recv(MSG_PEEK|MSG_WAITALL)
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kernel
Version: 7.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Sabrina Dubroca
QA Contact: Hangbin Liu
Depends On:
TreeView+ depends on / blocked
Reported: 2015-03-24 14:18 UTC by Enrico Scholz
Modified: 2015-11-19 21:48 UTC (History)
7 users (show)

Fixed In Version: kernel-3.10.0-306.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-11-19 21:48:24 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Linux Kernel 99461 0 None None None 2019-02-14 20:51:20 UTC
Red Hat Product Errata RHSA-2015:2152 0 normal SHIPPED_LIVE Important: kernel security, bug fix, and enhancement update 2015-11-20 00:56:02 UTC
Sourceware 18493 0 P2 RESOLVED Infinite loop/deadlock? in __libc_recv (fd=fd@entry=300, buf=buf@entry=0x7f6042880600, n=n@entry=5, flags=-1, flags@entr... 2021-01-28 09:35:57 UTC

Description Enrico Scholz 2015-03-24 14:18:42 UTC
Description of problem:

Kernel goes into a busy loop when it waits for more data in a recv(MSG_PEEK|MSG_WAITALL) call.


#include <stdlib.h>
#include <netinet/ip.h>

int main(void)
	struct sockaddr_in	addr = {
		.sin_family	= AF_INET,
		.sin_port	= htons(1234),
		.sin_addr	= { INADDR_ANY }
	int			conn;
	char			buf[16];

	int			s = socket(AF_INET, SOCK_STREAM, 0);

	bind(s, (void *)&addr, sizeof addr);
	listen(s, 1);

	conn = accept(s, NULL, 0);

	recv(conn, buf, sizeof buf, MSG_PEEK|MSG_WAITALL);
$ gcc x.c
$ a.out &

$ nc 1234

--> 'a.out' consumes 100% CPU

'a.out' stays alive and consumes CPU when the 'nc' connection is closed unclean (e.g. no TCP FIN/RST).  This can be used for DDOS attacks.

Version-Release number of selected component (if applicable):


How reproducible:


Comment 2 Jiri Pirko 2015-04-08 08:30:18 UTC
Upstream kernel behaves the same. MSG_WAITALL tells kernel to wait until whole buffer can be filled. Looks like the combination with MSG_PEEK is not handled properly in tcp_recvmsg:

                if (copied >= target) {
                        /* Do not sleep, just process backlog. */
                } else
                        sk_wait_data(sk, &timeo);

In case both MSG_PEEK and MSG_WAITALL are there, sk_wait_data is not called.

Comment 3 Hannes Frederic Sowa 2015-04-13 12:08:45 UTC
lock_sock (the only lock taken at that moment) is preemptible in process context, so it should not lead to a DoS situation. Albeit maybe we can do better and handle the situation where both flags are set more intelligent?

Comment 4 Dan Searle 2015-07-24 11:21:10 UTC
What's the status of this bug? Is it being worked on? Is there any way a fix can be expedited?

Comment 7 Sabrina Dubroca 2015-07-31 15:02:25 UTC
This bug has been fixed upstream (in David Miller's net tree):

Comment 8 Dan Searle 2015-07-31 15:05:06 UTC
Many thanks!

Comment 9 Rafael Aquini 2015-08-18 13:03:35 UTC
Patch(es) available on kernel-3.10.0-306.el7

Comment 11 Dan Searle 2015-08-18 13:48:49 UTC
Hi, thanks for the update.

Will this patch go into the 3.13.0 kernel branch? I'm hoping to get Ubuntu to suck it into their LTS kernel packages which seem to be built from the 3.13.0 branch.

Comment 14 errata-xmlrpc 2015-11-19 21:48:24 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.