Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160507151935.2B6DA332055@smtpvbsrv1.mitre.org>
Date: Sat,  7 May 2016 11:19:35 -0400 (EDT)
From: cve-assign@...re.org
To: carnil@...ian.org
Cc: cve-assign@...re.org, oss-security@...ts.openwall.com, dledford@...hat.com, secalert@...hat.com, benh@...ian.org
Subject: Re: CVE Request: Linux: IB/security: Restrict use of the write() interface'

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

> https://git.kernel.org/linus/e6bd18f57aad1a2d1ef40e646d03ed0f2515c9e3

> The drivers/infiniband stack uses write() as a replacement for
> bi-directional ioctl().  This is not safe. There are ways to
> trigger write calls that result in the return structure that
> is normally written to user space being shunted off to user
> specified kernel memory instead.

Use CVE-2016-4565.


> For long term, update the user space libraries and the kernel API
> to something that doesn't present the same security vulnerabilities
> (likely a structured ioctl() interface).

As far as we can tell, this statement does not imply that there is a
remaining known vulnerability after
e6bd18f57aad1a2d1ef40e646d03ed0f2515c9e3 - instead, this statement
only suggests a possible functionality problem, e.g., there might be
third-party code or in-development code that was attempting to rely on
write calls for a legitimate purpose, and this code has now stopped
working without an immediate workaround.

- -- 
CVE Assignment Team
M/S M300, 202 Burlington Road, Bedford, MA 01730 USA
[ A PGP key is available for encrypted communications at
  http://cve.mitre.org/cve/request_id.html ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJXLgZZAAoJEHb/MwWLVhi29cEP/0J4S+2R9nVMJlexim783uu+
YdU/ivYcTS6jxj3KuUPRZnmWWJbE4h/73/sa9H2pdu0CzR0LmqICeeP94zGO2Jn7
8zoEBst07RqisgNgZFu+TCgvmwemoPEEE9OkTmurQBh3r5lcmR9I6wJulXJ8n1l2
rXOw796aR5KoYYyl9cjDU9hU1ufvrMi6hDThEb8+THFpoTus/kyOFhnZ74B4kUux
EjqTdrSZIqneCi5EIY5xxCZYo4LlsXx5rlZF6Yqhcg1jC5G/6jtzIZSjws0ZVPY7
Ueen2yV37Ms3d1YdTSo4QBCzMon2sMC0j1Jj0Ov+g2jWbHZh6zU+V5z6Xjf8nH0B
TgKWdG/wYOpcY1si+lfZbtKQwHvM2i1RZP5mH6v/lggCYivA72Q+KPmDSdpIq395
YOFKWRfA8xarcfmeENhFLKjgp/QlZn26TAuMdzSvrcbkqqMUk/XHHcifR4J46gjI
vCu47kmL0hJV6Q0GhX9cZ2A2/8cXSjpxfgQTG3ifjtuxdugXHxXSOoEx9o36NVWH
1dt0L+YISIkh0yUx7lF5qQ1NoTMLnY2RHuKOeJFoRz8xyrbH5c4cizuyXYeFbKRC
C7uxW98W0OxbORLWpjrgcjFBCnIDWIrgGh9fJAECQS3gV6A5k1EmZDtSmMAhjzE+
LY6zu+JLlIGbCDdCOL/o
=Zjzu
-----END PGP SIGNATURE-----

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.