From: "Hillf Danton" <hillf.zj@alibaba-inc.com>
To: <charley.ashbringer@gmail.com>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Vulnerability [CVE-2014-4608] recurs in Linux 3.17.2-4.5
Date: Tue, 31 May 2016 16:16:30 +0800 [thread overview]
Message-ID: <005501d1bb14$bc9338c0$35b9aa40$@alibaba-inc.com> (raw)
In-Reply-To: <005101d1bb12$a184dea0$e48e9be0$@alibaba-inc.com>
>
> Dear Sir/Madam:
> I'm a postgraduate student majoring in information security and
> I'm very interested in software vulnerabilities, I think it's really
> fascinating and I'm doing some research about how to find
> vulnerabilities automatically. I have done some tests with Linux bug
> commits. And I found that the patch codes ( fixing CVE-2014-4608 )
> didn't appear in the version 3.17.2 to 4.5. I'm just wondering if this
> means the vulnerability ( CVE-2014-4608 ) recurs in Linux 3.17.2-4.5.
> If not, is it fixed in another way?
> Thanks for your time, I'll appreciate it very much if you can give
> an answer.
>
> p.s. here is the link to CVE-2014-4608 report
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=206a81c18401 \
> c0cde6e579164f752c4b147324ce
>
> Best regards
>
> ZhiJun DENG
> Cluster and Grid Computing Laboratory
> HuaZhong University Of Science And Technology
> 1037 Luoyu Road,Wuhan,430074,China
> Tel:+86 - 15527287870
>
> Email锛�506012274@qq.com
>
Hi ZhiJun DENG
In linux-4.7-rc1 the log says,
1, 206a81c18401 ("lzo: properly check for overruns") was reverted by
af958a38a60c ("Revert "lzo: properly check for overruns"")
2, then it was fixed in
72cf90124e8 ("lzo: check for length overrun in variable length encoding.")
btw, please send email in pure text to LKML.
Hillf
next parent reply other threads:[~2016-05-31 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <005101d1bb12$a184dea0$e48e9be0$@alibaba-inc.com>
2016-05-31 8:16 ` Hillf Danton [this message]
2016-05-31 6:48 刘长鸣
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='005501d1bb14$bc9338c0$35b9aa40$@alibaba-inc.com' \
--to=hillf.zj@alibaba-inc.com \
--cc=charley.ashbringer@gmail.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®