From: Greg KH <greg@kroah•com>
To: David Miller <davem@davemloft•net>
Cc: dreibh@iem•uni-due.de, akpm@linux-foundation•org,
vladislav.yasevich@hp•com, netdev@vger•kernel.org,
bugzilla-daemon@bugzilla•kernel.org, martin.becke@uni-due•de,
linux-sctp@vger•kernel.org, stable@kernel•org, sri@us•ibm.com
Subject: Re: [stable] [Bugme-new] [Bug 18592] New: Remote/local Denial of Service vulnerability in SCTP packet/chunk handling
Date: Thu, 23 Sep 2010 12:37:39 -0700 [thread overview]
Message-ID: <20100923193739.GA2809@kroah.com> (raw)
In-Reply-To: <20100923.122155.108788529.davem@davemloft.net>
On Thu, Sep 23, 2010 at 12:21:55PM -0700, David Miller wrote:
> From: Greg KH <greg@kroah•com>
> Date: Thu, 23 Sep 2010 11:05:15 -0700
>
> > On Sat, Sep 18, 2010 at 04:11:03PM +0200, Thomas Dreibholz wrote:
> >> Vlad's patch solves the problem. I hope this patch can go into the mailine
> >> kernel soon, in order to get distribution kernels fixed as soon as possible. It
> >> is relatively easy to trigger the denial of service problem, making all
> >> systems providing SCTP-based services vulnerable to a remote DoS attack.
> >>
> >> I have also been able to reproduce the problem with kernel 2.6.32, i.e. at
> >> least all kernels from 2.6.32 to 2.6.36 are affected.
> >
> > Is this in Linus's tree now? If so, does anyone have the git commit id?
>
> Should be: 4bdab43323b459900578b200a4b8cf9713ac8fab
Wonderful, now queued up.
thanks,
greg k-h
prev parent reply other threads:[~2010-09-23 19:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-18592-10286@https.bugzilla.kernel.org/>
2010-09-15 19:43 ` [Bugme-new] [Bug 18592] New: Remote/local Denial of Service vulnerability in SCTP packet/chunk handling Andrew Morton
2010-09-16 0:34 ` Vlad Yasevich
2010-09-18 14:11 ` Thomas Dreibholz
2010-09-23 18:05 ` [stable] " Greg KH
2010-09-23 19:21 ` David Miller
2010-09-23 19:37 ` Greg KH [this message]
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=20100923193739.GA2809@kroah.com \
--to=greg@kroah$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=bugzilla-daemon@bugzilla$(echo .)kernel.org \
--cc=davem@davemloft$(echo .)net \
--cc=dreibh@iem$(echo .)uni-due.de \
--cc=linux-sctp@vger$(echo .)kernel.org \
--cc=martin.becke@uni-due$(echo .)de \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sri@us$(echo .)ibm.com \
--cc=stable@kernel$(echo .)org \
--cc=vladislav.yasevich@hp$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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