From: Dick Snippe <Dick.Snippe@npo.nl>
To: stable@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: CVE-2015-1805 and 3.14-longterm?
Date: Thu, 2 Jul 2015 10:19:34 +0200 [thread overview]
Message-ID: <20150702081934.GA13480@npo.nl> (raw)
Hello,
I'm sorry to bother you with this, but lwn.net reported a rather serious
security issue a couple of weeks ago:
http://lwn.net/Articles/646590/
https://bugzilla.redhat.com/show_bug.cgi?id=1202855
CVE-2015-1805
"It was found that the Linux kernel's implementation of vectored pipe
read and write functionality did not take into account the I/O vectors
that were already processed when retrying after a failed atomic access
operation, potentially resulting in memory corruption due to an I/O
vector array overrun. A local, unprivileged user could use this flaw to
crash the system or, potentially, escalate their privileges on the
system."
It appears that these upstream fixes haven't made it to 3.14.4[456]:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f0d1bec9d58d4c038d0ac958c9af82be6eb18045
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=637b58c2887e5e57850865839cc75f59184b23d1
I'm just a (very happy!) user of the -longterm kernels, so I don't
know how this normally works. But it would appear that this bug still
exists in the -longterm kernels.
--
Dick Snippe, internetbeheerder NPO ICT team Media \ fight war
Postbus 26444, 1202 JJ Hilversum, servicedesk@npo.nl \ not wars
+31 35 6773555, Bart de Graaffweg 2, 1217 ZL Hilversum
next reply other threads:[~2015-07-02 8:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 8:19 Dick Snippe [this message]
2015-08-14 16:55 ` CVE-2015-1805 and 3.14-longterm? Greg KH
2015-08-14 19:17 ` Sven Joachim
2015-08-14 19:59 ` Greg KH
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=20150702081934.GA13480@npo.nl \
--to=dick.snippe@npo.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).