From: Jaco Kroon <jaco@kroon.co.za>
To: Greg KH <greg@kroah.com>
Cc: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
davem@davemloft.net, security@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] infinite recursion in netlink
Date: Thu, 26 Apr 2007 00:21:50 +0200 [thread overview]
Message-ID: <462FD47E.8020502@kroon.co.za> (raw)
In-Reply-To: <20070425195941.GA11699@kroah.com>
Greg KH wrote:
> On Wed, Apr 25, 2007 at 10:38:56PM +0400, Alexey Kuznetsov wrote:
>> Hello!
>>
>> Reply to NETLINK_FIB_LOOKUP messages were misrouted back to kernel,
>> which resulted in infinite recursion and stack overflow.
>>
>> The bug is present in all kernel versions since the feature appeared.
>
> Any hint on when this feature appeared so that we can notify the distros
> for older releases?
>
> thanks,
2.6.13 if I'm not mistaken, confirmed on debian testing by Simeon
Miteff. From man 7 netlink:
NETLINK_W1 and NETLINK_FIB_LOOKUP appeared in Linux 2.6.13.
Jaco
next prev parent reply other threads:[~2007-04-25 22:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 18:38 [PATCH] infinite recursion in netlink Alexey Kuznetsov
2007-04-25 19:59 ` Greg KH
2007-04-25 20:05 ` David Miller
2007-04-25 22:21 ` Jaco Kroon [this message]
2007-04-25 20:09 ` David Miller
2007-04-25 20:15 ` [Security] " Linus Torvalds
2007-04-25 20:18 ` David Miller
2007-04-26 5:29 ` Greg KH
2007-04-26 5:32 ` David Miller
2007-04-26 5:44 ` Greg KH
2007-04-26 5:48 ` Greg KH
2007-04-26 5:52 ` Chris Wright
2007-04-26 6:26 ` Chris Wright
2007-04-26 6:31 ` David Miller
2007-04-26 6:51 ` Greg KH
2007-04-26 7:02 ` David Miller
2007-04-26 5:37 ` Chris Wright
2007-04-26 15:44 ` [PATCH] [IPV4] nl_fib_lookup: Initialise res.r before fib_res_put(&res) Sergey Vlasov
2007-04-26 16:11 ` Alexey Kuznetsov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=462FD47E.8020502@kroon.co.za \
--to=jaco@kroon.co.za \
--cc=davem@davemloft.net \
--cc=greg@kroah.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=security@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.