Bug 1035658 - (CVE-2017-8070) VUL-0: CVE-2017-8070: kernel-source: drivers/net/usb/catc.c in the Linux kernel 4.9.x before 4.9.11 interactsincorrectly with the CONFIG...
(CVE-2017-8070)
VUL-0: CVE-2017-8070: kernel-source: drivers/net/usb/catc.c in the Linux kern...
Status: RESOLVED UPSTREAM
Classification: Novell Products
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents
unspecified
Other Other
: P3 - Medium : Normal
: ---
Assigned To: Security Team bot
Security Team bot
https://smash.suse.de/issue/184101/
CVSSv2:SUSE:CVE-2017-8070:3.3:(AV:L/A...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-04-24 09:10 UTC by Marcus Meissner
Modified: 2017-04-28 14:43 UTC (History)
4 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 2017-04-24 09:10:56 UTC
CVE-2017-8070

drivers/net/usb/catc.c in the Linux kernel 4.9.x before 4.9.11 interacts
incorrectly with the CONFIG_VMAP_STACK option, which allows local users to cause
a denial of service (system crash or memory corruption) or possibly have
unspecified other impact by leveraging use of more than one virtual page for a
DMA scatterlist.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-8070
http://www.cvedetails.com/cve/CVE-2017-8070/
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8070
https://github.com/torvalds/linux/commit/2d6a0e9de03ee658a9adc3bfb2f0ca55dff1e478
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2d6a0e9de03ee658a9adc3bfb2f0ca55dff1e478
Comment 1 Marcus Meissner 2017-04-24 09:31:08 UTC
(all kernels affected. catc driver is supported in SLE)
Comment 2 Michal Kubeček 2017-04-24 12:55:18 UTC
CONFIG_VMAP_STACK is only available since v4.9-rc1. As the fix is in v4.10-rc8
and TW is already on 4.10.x, it seems that none of our kernels needs fixing.
Comment 3 Takashi Iwai 2017-04-28 09:14:44 UTC
Reassigned back to security team.  Feel free to close.
Comment 4 Marcus Meissner 2017-04-28 11:20:52 UTC
fixed upstream, no current SUSE or openSUSE affected