Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1439768 - (CVE-2016-10318) CVE-2016-10318 kernel: User can assign an encryption policy to a directory owned by a different user
CVE-2016-10318 kernel: User can assign an encryption policy to a directory ow...
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=20160908,repor...
: Security
Depends On:
Blocks: 1439769
  Show dependency treegraph
 
Reported: 2017-04-06 09:39 EDT by Andrej Nemec
Modified: 2018-08-28 18:15 EDT (History)
31 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
A missing authorization check in the fscrypt_process_policy function in fs/crypto/policy.c in the ext4 and f2fs filesystem encryption support in the Linux kernel allows a user to assign an encryption policy to a directory owned by a different user, potentially creating a denial of service.
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 Andrej Nemec 2017-04-06 09:39:59 EDT
A missing authorization check in the fscrypt_process_policy function in fs/crypto/policy.c in the ext4 and f2fs filesystem encryption support in the Linux kernel allows a user to assign an encryption policy to a directory owned by a different user, potentially creating a denial of service.

Upstream patch:

https://github.com/torvalds/linux/commit/163ae1c6ad6299b19e22b4a35d5ab24a89791a98
Comment 2 Wade Mealing 2017-05-29 00:54:02 EDT
Statement:

This issue does not affect Red Hat Enterprise Linux 5, 6 and 7, MRG and realtime kernels.

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