Bug 1035681 - (CVE-2017-8064) VUL-0: CVE-2017-8064: kernel-source: drivers/media/usb/dvb-usb-v2/dvb_usb_core.c in the Linux kernel 4.9.x and 4.10.xbefore 4.10.12 inte...
(CVE-2017-8064)
VUL-0: CVE-2017-8064: kernel-source: drivers/media/usb/dvb-usb-v2/dvb_usb_cor...
Status: RESOLVED FIXED
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/184095/
CVSSv2:SUSE:CVE-2017-8064:3.3:(AV:L/A...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-04-24 10:49 UTC by Marcus Meissner
Modified: 2017-04-28 11:26 UTC (History)
3 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 10:49:13 UTC
CVE-2017-8064

drivers/media/usb/dvb-usb-v2/dvb_usb_core.c in the Linux kernel 4.9.x and 4.10.x
before 4.10.12 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-8064
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8064
https://github.com/torvalds/linux/commit/005145378c9ad7575a01b6ce1ba118fb427f583a
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=005145378c9ad7575a01b6ce1ba118fb427f583a
Comment 1 Marcus Meissner 2017-04-24 11:03:45 UTC
"struct device device" seems to be there for some time
Comment 2 Takashi Iwai 2017-04-24 14:12:16 UTC
CONFIG_VMAP_STACK is new in 4.9, and it's already fixed in the recent 4.10.x.
We are unaffected.
Comment 3 Takashi Iwai 2017-04-28 09:12:32 UTC
Reassigned back to security team.  Feel free to close.
Comment 4 Marcus Meissner 2017-04-28 11:26:32 UTC
fixed upstream, no current SUSE or openSUSE affected