linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomas Hozza <thozza@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
	olaf@aepfle.de, apw@canonical.com, jasowang@redhat.com,
	kys@microsoft.com
Subject: Re: [PATCH] tools: hv: Netlink source address validation allows DoS
Date: Sun, 18 Nov 2012 09:21:57 -0500 (EST)	[thread overview]
Message-ID: <1900142520.231739.1353248517842.JavaMail.root@redhat.com> (raw)
In-Reply-To: <20121115233909.GA17580@kroah.com>

Hello.

Just FYI there is already a CVE name CVE-2012-5532 for this issue.

Regards,
Tomas Hozza

----- Original Message -----
> On Thu, Nov 08, 2012 at 10:53:29AM +0100, Tomas Hozza wrote:
> > The source code without this patch caused hypervkvpd to exit when
> > it processed
> > a spoofed Netlink packet which has been sent from an untrusted
> > local user.
> > Now Netlink messages with a non-zero nl_pid source address are
> > ignored
> > and a warning is printed into the syslog.
> > 
> > Signed-off-by: Tomas Hozza <thozza@redhat.com>
> > Acked-by:  K. Y. Srinivasan <kys@microsoft.com>
> > ---
> >  tools/hv/hv_kvp_daemon.c | 8 +++++++-
> >  1 file changed, 7 insertions(+), 1 deletion(-)
> > 
> > diff --git a/tools/hv/hv_kvp_daemon.c b/tools/hv/hv_kvp_daemon.c
> > index 13c2a14..c1d9102 100755
> 
> Why are you setting a .c file to executable permissions?  Something
> is
> really wrong here...
> 
> greg k-h
> 

  parent reply	other threads:[~2012-11-18 14:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-08  9:53 [PATCH] tools: hv: Netlink source address validation allows DoS Tomas Hozza
2012-11-08 13:18 ` KY Srinivasan
2012-11-15 23:39 ` Greg KH
2012-11-16  7:21   ` Tomas Hozza
2012-11-18 14:21   ` Tomas Hozza [this message]
     [not found] <20121106152911.GA1591@kroah.com>
2012-11-07  8:17 ` Tomas Hozza

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=1900142520.231739.1353248517842.JavaMail.root@redhat.com \
    --to=thozza@redhat.com \
    --cc=apw@canonical.com \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jasowang@redhat.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf@aepfle.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).