RHSA-2016:2574
Vulnerability from csaf_redhat - Published: 2016-11-03 08:06 - Updated: 2026-06-28 12:28It was found that the Linux kernel did not properly account file descriptors passed over the unix socket against the process limit. A local user could use this flaw to exhaust all available memory on the system.
| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: 7Client-optional:kernel-debug-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Client-optional:kernel-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Client-optional:kernel-debuginfo-common-x86_64-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Client-optional:kernel-tools-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Client-optional:kernel-tools-libs-devel-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Client-optional:perf-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Client-optional:python-perf-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Client:kernel-0:3.10.0-514.el7.src | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Client:kernel-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Client:kernel-abi-whitelists-0:3.10.0-514.el7.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Client:kernel-debug-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Client:kernel-debug-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Client:kernel-debug-devel-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Client:kernel-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Client:kernel-debuginfo-common-x86_64-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Client:kernel-devel-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Client:kernel-doc-0:3.10.0-514.el7.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Client:kernel-headers-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Client:kernel-tools-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Client:kernel-tools-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Client:kernel-tools-libs-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Client:perf-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Client:perf-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Client:python-perf-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Client:python-perf-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode-optional:kernel-debug-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode-optional:kernel-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode-optional:kernel-debuginfo-common-x86_64-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode-optional:kernel-tools-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode-optional:kernel-tools-libs-devel-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode-optional:perf-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode-optional:python-perf-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode:kernel-0:3.10.0-514.el7.src | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode:kernel-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode:kernel-abi-whitelists-0:3.10.0-514.el7.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode:kernel-debug-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode:kernel-debug-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode:kernel-debug-devel-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode:kernel-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode:kernel-debuginfo-common-x86_64-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode:kernel-devel-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode:kernel-doc-0:3.10.0-514.el7.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode:kernel-headers-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode:kernel-tools-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode:kernel-tools-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode:kernel-tools-libs-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode:perf-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode:perf-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode:python-perf-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7ComputeNode:python-perf-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server-optional:kernel-debug-debuginfo-0:3.10.0-514.el7.ppc64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server-optional:kernel-debug-debuginfo-0:3.10.0-514.el7.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server-optional:kernel-debug-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server-optional:kernel-debug-devel-0:3.10.0-514.el7.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server-optional:kernel-debuginfo-0:3.10.0-514.el7.ppc64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server-optional:kernel-debuginfo-0:3.10.0-514.el7.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server-optional:kernel-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server-optional:kernel-debuginfo-common-ppc64-0:3.10.0-514.el7.ppc64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server-optional:kernel-debuginfo-common-ppc64le-0:3.10.0-514.el7.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server-optional:kernel-debuginfo-common-x86_64-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server-optional:kernel-tools-debuginfo-0:3.10.0-514.el7.ppc64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server-optional:kernel-tools-debuginfo-0:3.10.0-514.el7.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server-optional:kernel-tools-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server-optional:kernel-tools-libs-devel-0:3.10.0-514.el7.ppc64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server-optional:kernel-tools-libs-devel-0:3.10.0-514.el7.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server-optional:kernel-tools-libs-devel-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server-optional:perf-debuginfo-0:3.10.0-514.el7.ppc64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server-optional:perf-debuginfo-0:3.10.0-514.el7.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server-optional:perf-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server-optional:python-perf-debuginfo-0:3.10.0-514.el7.ppc64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server-optional:python-perf-debuginfo-0:3.10.0-514.el7.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server-optional:python-perf-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-0:3.10.0-514.el7.ppc64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-0:3.10.0-514.el7.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-0:3.10.0-514.el7.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-0:3.10.0-514.el7.src | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-abi-whitelists-0:3.10.0-514.el7.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-bootwrapper-0:3.10.0-514.el7.ppc64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-bootwrapper-0:3.10.0-514.el7.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-debug-0:3.10.0-514.el7.ppc64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-debug-0:3.10.0-514.el7.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-debug-0:3.10.0-514.el7.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-debug-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-debug-debuginfo-0:3.10.0-514.el7.ppc64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-debug-debuginfo-0:3.10.0-514.el7.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-debug-debuginfo-0:3.10.0-514.el7.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-debug-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-debug-devel-0:3.10.0-514.el7.ppc64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-debug-devel-0:3.10.0-514.el7.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-debug-devel-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-debuginfo-0:3.10.0-514.el7.ppc64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-debuginfo-0:3.10.0-514.el7.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-debuginfo-0:3.10.0-514.el7.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-debuginfo-common-ppc64-0:3.10.0-514.el7.ppc64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-debuginfo-common-ppc64le-0:3.10.0-514.el7.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-debuginfo-common-s390x-0:3.10.0-514.el7.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-debuginfo-common-x86_64-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-devel-0:3.10.0-514.el7.ppc64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-devel-0:3.10.0-514.el7.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-devel-0:3.10.0-514.el7.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-devel-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-doc-0:3.10.0-514.el7.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-headers-0:3.10.0-514.el7.ppc64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-headers-0:3.10.0-514.el7.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-headers-0:3.10.0-514.el7.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-headers-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-kdump-0:3.10.0-514.el7.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-kdump-debuginfo-0:3.10.0-514.el7.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-kdump-devel-0:3.10.0-514.el7.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-tools-0:3.10.0-514.el7.ppc64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-tools-0:3.10.0-514.el7.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-tools-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-tools-debuginfo-0:3.10.0-514.el7.ppc64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-tools-debuginfo-0:3.10.0-514.el7.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-tools-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-tools-libs-0:3.10.0-514.el7.ppc64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-tools-libs-0:3.10.0-514.el7.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:kernel-tools-libs-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:perf-0:3.10.0-514.el7.ppc64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:perf-0:3.10.0-514.el7.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:perf-0:3.10.0-514.el7.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:perf-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:perf-debuginfo-0:3.10.0-514.el7.ppc64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:perf-debuginfo-0:3.10.0-514.el7.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:perf-debuginfo-0:3.10.0-514.el7.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:perf-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:python-perf-0:3.10.0-514.el7.ppc64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:python-perf-0:3.10.0-514.el7.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:python-perf-0:3.10.0-514.el7.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:python-perf-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:python-perf-debuginfo-0:3.10.0-514.el7.ppc64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:python-perf-debuginfo-0:3.10.0-514.el7.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:python-perf-debuginfo-0:3.10.0-514.el7.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Server:python-perf-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation-optional:kernel-debug-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation-optional:kernel-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation-optional:kernel-debuginfo-common-x86_64-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation-optional:kernel-tools-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation-optional:kernel-tools-libs-devel-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation-optional:perf-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation-optional:python-perf-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation:kernel-0:3.10.0-514.el7.src | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation:kernel-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation:kernel-abi-whitelists-0:3.10.0-514.el7.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation:kernel-debug-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation:kernel-debug-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation:kernel-debug-devel-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation:kernel-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation:kernel-debuginfo-common-x86_64-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation:kernel-devel-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation:kernel-doc-0:3.10.0-514.el7.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation:kernel-headers-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation:kernel-tools-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation:kernel-tools-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation:kernel-tools-libs-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation:perf-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation:perf-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation:python-perf-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: 7Workstation:python-perf-debuginfo-0:3.10.0-514.el7.x86_64 | — |
Vendor Fix
fix
|
An information-leak vulnerability was found in the kernel when it truncated a file to a smaller size which consisted of an inline extent that was compressed. The data between the new file size and the old file size was not discarded and the number of bytes used by the inode were not correctly decremented, which gave the wrong report for callers of the stat(2) syscall. This wasted metadata space and allowed for the truncated data to be leaked, and data corruption or loss to occur. A caller of the clone ioctl could exploit this flaw by using only standard file-system operations without root access to read the truncated data.
A NULL pointer dereference flaw was found in the way the Linux kernel's network subsystem handled socket creation with an invalid protocol identifier. A local user could use this flaw to crash the system.
A NULL pointer dereference flaw was found in the Linux kernel: the NFSv4.2 migration code improperly initialized the kernel structure. A local, authenticated user could use this flaw to cause a panic of the NFS client (denial of service).
A use-after-free flaw was found in the CXGB3 kernel driver when the network was considered to be congested. The kernel incorrectly misinterpreted the congestion as an error condition and incorrectly freed or cleaned up the socket buffer (skb). When the device then sent the skb's queued data, these structures were referenced. A local attacker could use this flaw to panic the system (denial of service) or, with a local account, escalate their privileges.
A flaw was found in the Linux kernel which could cause a kernel panic when restoring machine specific registers on the PowerPC platform. Incorrect transactional memory state registers could inadvertently change the call path on return from userspace and cause the kernel to enter an unknown state and crash.
A flaw was found in the Linux kernel which could cause a kernel panic when restoring machine specific registers on the PowerPC platform. Incorrect transactional memory state registers could inadvertently change the call path on return from userspace and cause the kernel to enter an unknown state and crash.
The rfcomm_sock_bind function in net/bluetooth/rfcomm/sock.c in the Linux kernel before 4.2 allows local users to obtain sensitive information or cause a denial of service (NULL pointer dereference) via vectors involving a bind system call on a Bluetooth RFCOMM socket.
A syntax vulnerability was discovered in the kernel's ASN1.1 DER decoder, which could lead to memory corruption or a complete local denial of service through x509 certificate DER files. A local system user could use a specially created key file to trigger BUG_ON() in the public_key_verify_signature() function (crypto/asymmetric_keys/public_key.c), to cause a kernel panic and crash the system.
A flaw was discovered in the way the Linux kernel dealt with paging structures. When the kernel invalidated a paging structure that was not in use locally, it could, in principle, race against another CPU that is switching to a process that uses the paging structure in question. A local user could use a thread running with a stale cached virtual->physical translation to potentially escalate their privileges if the translation in question were writable and the physical page got reused for something critical (for example, a page table).
It was discovered that the atl2_probe() function in the Atheros L2 Ethernet driver in the Linux kernel incorrectly enabled scatter/gather I/O. A remote attacker could use this flaw to obtain potentially sensitive information from the kernel memory.
A flaw was found in the USB-MIDI Linux kernel driver: a double-free error could be triggered for the 'umidi' object. An attacker with physical access to the system could use this flaw to escalate their privileges.
It is possible for a single process to cause an OOM condition by filling large pipes with data that are never read. A typical process filling 4096 pipes with 1 MB of data will use 4 GB of memory and there can be multiple such processes, up to a per-user-limit.
The Linux kernel component in IBM PowerKVM 2.1 before 2.1.1.3-65.10 and 3.1 before 3.1.0.2 allows guest OS users to cause a denial of service (host OS infinite loop and hang) via unspecified vectors.
A security flaw was found in the Linux kernel that an attempt to move page mapped by AIO ring buffer to the other node triggers NULL pointer dereference at trace_writeback_dirty_page(), because aio_fs_backing_dev_info.dev is 0.
A security flaw was found in the Linux kernel's networking subsystem that destroying the network interface with huge number of ipv4 addresses assigned keeps "rtnl_lock" spinlock for a very long time (up to hour). This blocks many network-related operations, including creation of new incoming ssh connections. The problem is especially important for containers, as the container owner has enough permissions to trigger this and block a network access on a whole host, outside the container.
The Linux kernel, as used in Red Hat Enterprise Linux 7.2 and Red Hat Enterprise MRG 2 and when booted with UEFI Secure Boot enabled, allows local users to bypass intended Secure Boot restrictions and execute untrusted code by appending ACPI tables to the initrd.
It was found that the Linux kernel's IPv6 implementation mishandled socket options. A local attacker could abuse concurrent access to the socket options to escalate their privileges, or cause a denial of service (use-after-free and system crash) via a crafted sendmsg system call.
A vulnerability was found in Linux kernel. There is an information leak in file "sound/core/timer.c" of the latest mainline Linux kernel, the stack object “tread” has a total size of 32 bytes. It contains a 8-bytes padding, which is not initialized but sent to user via copy_to_user(), resulting a kernel leak.
A vulnerability was found in Linux kernel. There is an information leak in file sound/core/timer.c of the latest mainline Linux kernel. The stack object “r1” has a total size of 32 bytes. Its field “event” and “val” both contain 4 bytes padding. These 8 bytes padding bytes are sent to user without being initialized.
fs/pnode.c in the Linux kernel before 4.5.4 does not properly traverse a mount propagation tree in a certain case involving a slave mount, which allows local users to cause a denial of service (NULL pointer dereference and OOPS) via a crafted series of mount system calls.
Use after free vulnerability was found in percpu using previously allocated memory in bpf. First __alloc_percpu_gfp() is called, then the memory is freed with free_percpu() which triggers async pcpu_balance_work and then pcpu_extend_area_map could use a chunk after it has been freed.
arch/powerpc/kvm/book3s_hv_rmhandlers.S in the Linux kernel through 4.7 on PowerPC platforms, when CONFIG_KVM_BOOK3S_64_HV is enabled, allows guest OS users to cause a denial of service (host OS infinite loop) by making a H_CEDE hypercall during the existence of a suspended transaction.
A vulnerability in the handling of Transactional Memory on powerpc systems was found. An unprivileged local user can crash the kernel by starting a transaction, suspending it, and then calling any of the exec() class system calls.
A heap-based buffer overflow vulnerability was found in the Linux kernel's hiddev driver. This flaw could allow a local attacker to corrupt kernel memory, possible privilege escalation or crashing the system.
When creating audit records for parameters to executed children processes, an attacker can convince the Linux kernel audit subsystem can create corrupt records which may allow an attacker to misrepresent or evade logging of executing commands.
A flaw was found that the vfs_rename() function did not detect hard links on overlayfs. A local, unprivileged user could use the rename syscall on overlayfs on top of xfs to crash the system.
System using the infiniband support module ib_srpt were vulnerable to a denial of service by system crash by a local attacker who is able to abort writes to a device using this initiator.
A race condition flaw was found in the ioctl_send_fib() function in the Linux kernel's aacraid implementation. A local attacker could use this flaw to cause a denial of service (out-of-bounds access or system crash) by changing a certain size value.
The assoc_array_insert_into_terminal_node() function in 'lib/assoc_array.c' in the Linux kernel before 4.5.3 does not check whether a slot is a leaf, which allows local users to obtain sensitive information from kernel memory or cause a denial of service (invalid pointer dereference and out-of-bounds read) via an application that uses associative-array data structures.
The hid_input_field() function in 'drivers/hid/hid-core.c' in the Linux kernel before 4.6 allows physically proximate attackers to obtain sensitive information from kernel memory or cause a denial of service (out-of-bounds read) by connecting a device.
CWE-125 - Out-of-bounds ReadA use-after-free vulnerability was found in ALSA pcm layer, which allows local users to cause a denial of service, memory corruption, or possibly other unspecified impact. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although we believe it is unlikely.
A race condition was found in the Linux kernel's sound timer code in the snd_timer_user_read() function in the sound/core/timer.c file. An unprivileged attacker can exploit the race condition to cause an out-of-bound access which may lead to a system crash or other unspecified impact. Due to the nature of the flaw, privilege escalation cannot be fully ruled out.
CWE-362 - Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')An issue was discovered in the Linux kernel where an incorrect access check in overlayfs mounts could be used by local attackers to modify or truncate files in the underlying filesystem.
Loading 1.3 MB of JSON…
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.