The filesystem implementation in the Linux kernel through 4.8.2 preserves the setgid bit during a setxattr call, which allows local users to gain group privileges by leveraging the existence of a setgid program with restrictions on execute permissions.
The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Linux_kernel | Linux | * | 4.8.2 (including) |
Red Hat Enterprise Linux 6 | RedHat | kernel-0:2.6.32-696.el6 | * |
Red Hat Enterprise Linux 7 | RedHat | kernel-rt-0:3.10.0-693.rt56.617.el7 | * |
Red Hat Enterprise Linux 7 | RedHat | kernel-0:3.10.0-693.el7 | * |
Red Hat Enterprise MRG 2 | RedHat | kernel-rt-1:3.10.0-693.2.1.rt56.585.el6rt | * |
Linux | Ubuntu | precise | * |
Linux | Ubuntu | precise/esm | * |
Linux | Ubuntu | trusty | * |
Linux | Ubuntu | upstream | * |
Linux | Ubuntu | vivid/ubuntu-core | * |
Linux | Ubuntu | xenial | * |
Linux | Ubuntu | yakkety | * |
Linux-armadaxp | Ubuntu | precise | * |
Linux-armadaxp | Ubuntu | upstream | * |
Linux-aws | Ubuntu | upstream | * |
Linux-azure | Ubuntu | upstream | * |
Linux-euclid | Ubuntu | upstream | * |
Linux-flo | Ubuntu | esm-apps/xenial | * |
Linux-flo | Ubuntu | trusty | * |
Linux-flo | Ubuntu | upstream | * |
Linux-flo | Ubuntu | vivid/stable-phone-overlay | * |
Linux-flo | Ubuntu | xenial | * |
Linux-flo | Ubuntu | yakkety | * |
Linux-gcp | Ubuntu | upstream | * |
Linux-gke | Ubuntu | upstream | * |
Linux-goldfish | Ubuntu | esm-apps/xenial | * |
Linux-goldfish | Ubuntu | trusty | * |
Linux-goldfish | Ubuntu | upstream | * |
Linux-goldfish | Ubuntu | xenial | * |
Linux-goldfish | Ubuntu | yakkety | * |
Linux-goldfish | Ubuntu | zesty | * |
Linux-grouper | Ubuntu | trusty | * |
Linux-grouper | Ubuntu | upstream | * |
Linux-hwe | Ubuntu | upstream | * |
Linux-hwe-edge | Ubuntu | upstream | * |
Linux-kvm | Ubuntu | upstream | * |
Linux-linaro-omap | Ubuntu | precise | * |
Linux-linaro-omap | Ubuntu | upstream | * |
Linux-linaro-shared | Ubuntu | precise | * |
Linux-linaro-shared | Ubuntu | upstream | * |
Linux-linaro-vexpress | Ubuntu | precise | * |
Linux-linaro-vexpress | Ubuntu | upstream | * |
Linux-lts-quantal | Ubuntu | precise | * |
Linux-lts-quantal | Ubuntu | precise/esm | * |
Linux-lts-quantal | Ubuntu | upstream | * |
Linux-lts-raring | Ubuntu | precise | * |
Linux-lts-raring | Ubuntu | precise/esm | * |
Linux-lts-raring | Ubuntu | upstream | * |
Linux-lts-saucy | Ubuntu | precise | * |
Linux-lts-saucy | Ubuntu | precise/esm | * |
Linux-lts-saucy | Ubuntu | upstream | * |
Linux-lts-trusty | Ubuntu | precise | * |
Linux-lts-trusty | Ubuntu | upstream | * |
Linux-lts-utopic | Ubuntu | trusty | * |
Linux-lts-utopic | Ubuntu | upstream | * |
Linux-lts-vivid | Ubuntu | trusty | * |
Linux-lts-vivid | Ubuntu | trusty/esm | * |
Linux-lts-vivid | Ubuntu | upstream | * |
Linux-lts-wily | Ubuntu | trusty | * |
Linux-lts-wily | Ubuntu | upstream | * |
Linux-lts-xenial | Ubuntu | trusty | * |
Linux-lts-xenial | Ubuntu | upstream | * |
Linux-maguro | Ubuntu | trusty | * |
Linux-maguro | Ubuntu | upstream | * |
Linux-mako | Ubuntu | esm-apps/xenial | * |
Linux-mako | Ubuntu | trusty | * |
Linux-mako | Ubuntu | upstream | * |
Linux-mako | Ubuntu | vivid/stable-phone-overlay | * |
Linux-mako | Ubuntu | xenial | * |
Linux-mako | Ubuntu | yakkety | * |
Linux-manta | Ubuntu | trusty | * |
Linux-manta | Ubuntu | upstream | * |
Linux-oem | Ubuntu | upstream | * |
Linux-qcm-msm | Ubuntu | precise | * |
Linux-qcm-msm | Ubuntu | upstream | * |
Linux-raspi2 | Ubuntu | upstream | * |
Linux-raspi2 | Ubuntu | vivid/ubuntu-core | * |
Linux-raspi2 | Ubuntu | xenial | * |
Linux-raspi2 | Ubuntu | yakkety | * |
Linux-snapdragon | Ubuntu | upstream | * |
Linux-snapdragon | Ubuntu | xenial | * |
Linux-snapdragon | Ubuntu | yakkety | * |
Linux-ti-omap4 | Ubuntu | precise | * |
Linux-ti-omap4 | Ubuntu | upstream | * |
Assuming a user with a given identity, authorization is the process of determining whether that user can access a given resource, based on the user’s privileges and any permissions or other access-control specifications that apply to the resource. When access control checks are not applied consistently - or not at all - users are able to access data or perform actions that they should not be allowed to perform. This can lead to a wide range of problems, including information exposures, denial of service, and arbitrary code execution.