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 1529120 - (CVE-2017-17864) CVE-2017-17864 kernel: information disclosure via pointer leak in kernel/bpf/verifier.c
CVE-2017-17864 kernel: information disclosure via pointer leak in kernel/bpf/...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20171223,reported=2...
: Security
Depends On: 1535008 1529125
Blocks: 1528364
  Show dependency treegraph
 
Reported: 2017-12-26 09:26 EST by Pedro Sampaio
Modified: 2018-08-28 18:29 EDT (History)
43 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 Pedro Sampaio 2017-12-26 09:26:56 EST
kernel/bpf/verifier.c in the Linux kernel through 4.14.8 mishandles states_equal comparisons between the pointer data type and the UNKNOWN_VALUE data type, which allows local users to obtain potentially sensitive address information, aka a "pointer leak."

References:

https://anonscm.debian.org/cgit/kernel/linux.git/tree/debian/patches/bugfix/all/bpf-verifier-fix-states_equal-comparison-of-pointer-and-unknown.patch?h=stretch-security
https://anonscm.debian.org/cgit/kernel/linux.git/commit/?h=stretch-security&id=ad775f6ff7eebb93eedc2f592bc974260e7757b0
Comment 1 Pedro Sampaio 2017-12-26 09:48:04 EST
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1529125]
Comment 3 Prasad J Pandit 2018-01-18 00:22:39 EST
Statement:

This issue does not affect the versions of the kernel package as shipped with Red Hat Enterprise Linux 5, 6, 7 and Red Hat Enterprise MRG 2.

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