The tm_reclaim_thread function in arch/powerpc/kernel/process.c in the Linux kernel before 4.4.1 on powerpc platforms does not ensure that TM suspend mode exists before proceeding with a tm_reclaim call, which allows local users to cause a denial of service (TM Bad Thing exception and panic) via a crafted application.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Linux_kernel | Linux | * | 4.4 (including) |
Red Hat Enterprise Linux 7 | RedHat | kernel-rt-0:3.10.0-514.rt56.420.el7 | * |
Red Hat Enterprise Linux 7 | RedHat | kernel-0:3.10.0-514.el7 | * |
Linux | Ubuntu | trusty | * |
Linux | Ubuntu | upstream | * |
Linux | Ubuntu | vivid/ubuntu-core | * |
Linux | Ubuntu | wily | * |
Linux-armadaxp | Ubuntu | upstream | * |
Linux-aws | Ubuntu | upstream | * |
Linux-flo | Ubuntu | trusty | * |
Linux-flo | Ubuntu | upstream | * |
Linux-gke | Ubuntu | upstream | * |
Linux-goldfish | Ubuntu | trusty | * |
Linux-goldfish | Ubuntu | upstream | * |
Linux-grouper | Ubuntu | trusty | * |
Linux-grouper | Ubuntu | upstream | * |
Linux-hwe | Ubuntu | upstream | * |
Linux-hwe-edge | 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 | upstream | * |
Linux-lts-wily | Ubuntu | trusty | * |
Linux-lts-wily | Ubuntu | upstream | * |
Linux-lts-xenial | Ubuntu | upstream | * |
Linux-maguro | Ubuntu | trusty | * |
Linux-maguro | Ubuntu | upstream | * |
Linux-mako | Ubuntu | trusty | * |
Linux-mako | Ubuntu | upstream | * |
Linux-manta | Ubuntu | trusty | * |
Linux-manta | 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 | wily | * |
Linux-snapdragon | Ubuntu | upstream | * |
Linux-ti-omap4 | Ubuntu | upstream | * |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: