Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1594170 - (CVE-2018-12633) CVE-2018-12633 kernel: Double-fetch vulnerability in drivers/virt/vboxguest/vboxguest_linux.c:vbg_misc_device_ioctl() allows information leak and local denial of service
CVE-2018-12633 kernel: Double-fetch vulnerability in drivers/virt/vboxguest/v...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20180508,repor...
: Security
Depends On: 1594173 1594172
Blocks:
  Show dependency treegraph
 
Reported: 2018-06-22 05:54 EDT by Adam Mariš
Modified: 2018-08-28 18:47 EDT (History)
41 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Adam Mariš 2018-06-22 05:54:14 EDT
An issue was discovered in the Linux kernel through 4.17.2. vbg_misc_device_ioctl() in drivers/virt/vboxguest/vboxguest_linux.c reads the same user data twice with copy_from_user. The header part of the user data is double-fetched, and a malicious user thread can tamper with the critical variables (hdr.size_in and hdr.size_out) in the header between the two fetches because of a race condition, leading to severe kernel errors, such as buffer over-accesses. This bug can cause a local denial of service and information leakage.

References:

https://bugzilla.kernel.org/show_bug.cgi?id=200131
https://github.com/torvalds/linux/commit/bd23a7269834dc7c1f93e83535d16ebc44b75eba
Comment 1 Adam Mariš 2018-06-22 06:01:25 EDT
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1594172]

Note You need to log in before you can comment on or make changes to this bug.