Bug 1120258 - (CVE-2018-16885) VUL-0: CVE-2018-16885: kernel-source: kernel: out-of-bound read in memcpy_fromiovecend()
(CVE-2018-16885)
VUL-0: CVE-2018-16885: kernel-source: kernel: out-of-bound read in memcpy_fro...
Status: RESOLVED INVALID
Classification: Novell Products
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents
unspecified
Other Other
: P3 - Medium : Normal
: ---
Assigned To: Michal Kubeček
Security Team bot
https://smash.suse.de/issue/221531/
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-12-22 13:34 UTC by Marcus Meissner
Modified: 2019-11-08 16:19 UTC (History)
5 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus Meissner 2018-12-22 13:34:29 UTC
rh#1661503

A flaw was found in the Linux kernel that allows the userspace to call memcpy_fromiovecend() and similar functions with a zero offset and buffer length which causes the read beyond the buffer boundaries, in certain cases causing a memory access fault and a system halt by accessing invalid memory address.

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1661503
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-16885
Comment 1 Marcus Meissner 2018-12-22 13:35:21 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=1661503


(In reply to Nicholas Luedtke from comment #3)
> Any more information on this? Fixing commit and/or introducing commit?

Hello, Nicholas,
I apologize for not mentioning previously that this is a RHEL-only bug.

This specific bug is indirectly fixed upstream by UFO removal, and
the buggy memcpy_fromiovecend() (and related functions) are fixed by:

commit 21226abb4e9f14d88238964d89b279e461ddc30c
Author: Al Viro <viro@zeniv.linux.org.uk>
Date: Fri Nov 28 15:48:29 2014 -0500
net: switch memcpy_fromiovec()/memcpy_fromiovecend() users to copy_from_iter()
Comment 4 Marcus Meissner 2019-11-08 16:19:20 UTC
would currently classify as not affected.