From: Willy Tarreau <w@1wt.eu>
To: Steven Pease <spease@suitabletech.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CVE-2016-10229 in 4.4.x series
Date: Tue, 16 May 2017 08:06:13 +0200 [thread overview]
Message-ID: <20170516060613.GA17551@1wt.eu> (raw)
In-Reply-To: <CALQ-SODhbky=pHUK1c6S91OE0H+kBS=7UATSNBud82a-hAunQA@mail.gmail.com>
On Mon, May 15, 2017 at 10:53:50PM -0700, Steven Pease wrote:
> Is there any particular reason that the CVE appears to be filed
> against 4.4.60? Or is this just a mistake?
>
> http://www.cvedetails.com/cve/CVE-2016-10229/
I have no idea why. Maybe they mentionned the current version at the
moment the CVE was issued (which seems to match). In fact this bug was
discovered as being a vulnerability long after the bug was fixed.
Willy
prev parent reply other threads:[~2017-05-16 6:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 1:09 Steven Pease
2017-05-16 5:20 ` Willy Tarreau
2017-05-16 5:53 ` Steven Pease
2017-05-16 6:06 ` Willy Tarreau [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=20170516060613.GA17551@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=spease@suitabletech.com \
/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
Powered by JetHome