lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 2 Jul 2015 10:19:34 +0200
From:	Dick Snippe <Dick.Snippe@....nl>
To:	stable@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org
Subject: CVE-2015-1805 and 3.14-longterm?

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@....nl  \ not wars
+31 35 6773555, Bart de Graaffweg 2, 1217 ZL Hilversum
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ