RHSA-2020:4060
Vulnerability from csaf_redhat - Published: 2020-09-29 22:31 - Updated: 2026-06-28 08:46An out of bounds (OOB) memory access flaw was found in i2c_smbus_xfer_emulated in drivers/i2c/i2c-core-smbus.c in I2C subsystem. A read request for length (data->block[0]) greater than 'I2C_SMBUS_BLOCK_MAX + 1' may cause underlying I2C driver write out of array's boundary. This could allow a local attacker with special user privilege (or root) to crash the system or leak kernel internal information.
| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: 7Client-7.9:bpftool-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-7.9:bpftool-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-7.9:kernel-0:3.10.0-1160.el7.src | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-7.9:kernel-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-7.9:kernel-abi-whitelists-0:3.10.0-1160.el7.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-7.9:kernel-debug-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-7.9:kernel-debug-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-7.9:kernel-debug-devel-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-7.9:kernel-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-7.9:kernel-debuginfo-common-x86_64-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-7.9:kernel-devel-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-7.9:kernel-doc-0:3.10.0-1160.el7.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-7.9:kernel-tools-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-7.9:kernel-tools-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-7.9:kernel-tools-libs-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-7.9:perf-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-7.9:perf-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-7.9:python-perf-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-7.9:python-perf-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-optional-7.9:bpftool-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-optional-7.9:kernel-debug-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-optional-7.9:kernel-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-optional-7.9:kernel-debuginfo-common-x86_64-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-optional-7.9:kernel-tools-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-optional-7.9:kernel-tools-libs-devel-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-optional-7.9:perf-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Client-optional-7.9:python-perf-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-7.9:bpftool-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-7.9:bpftool-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-7.9:kernel-0:3.10.0-1160.el7.src | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-7.9:kernel-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-7.9:kernel-abi-whitelists-0:3.10.0-1160.el7.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-7.9:kernel-debug-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-7.9:kernel-debug-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-7.9:kernel-debug-devel-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-7.9:kernel-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-7.9:kernel-debuginfo-common-x86_64-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-7.9:kernel-devel-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-7.9:kernel-doc-0:3.10.0-1160.el7.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-7.9:kernel-tools-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-7.9:kernel-tools-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-7.9:kernel-tools-libs-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-7.9:perf-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-7.9:perf-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-7.9:python-perf-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-7.9:python-perf-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-optional-7.9:bpftool-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-optional-7.9:kernel-debug-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-optional-7.9:kernel-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-optional-7.9:kernel-debuginfo-common-x86_64-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-optional-7.9:kernel-tools-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-optional-7.9:kernel-tools-libs-devel-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-optional-7.9:perf-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7ComputeNode-optional-7.9:python-perf-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:bpftool-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:bpftool-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:bpftool-0:3.10.0-1160.el7.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:bpftool-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:bpftool-debuginfo-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:bpftool-debuginfo-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:bpftool-debuginfo-0:3.10.0-1160.el7.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:bpftool-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-0:3.10.0-1160.el7.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-0:3.10.0-1160.el7.src | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-abi-whitelists-0:3.10.0-1160.el7.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-bootwrapper-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-bootwrapper-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-debug-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-debug-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-debug-0:3.10.0-1160.el7.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-debug-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-debug-debuginfo-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-debug-debuginfo-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-debug-debuginfo-0:3.10.0-1160.el7.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-debug-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-debug-devel-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-debug-devel-0:3.10.0-1160.el7.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-debug-devel-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-debuginfo-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-debuginfo-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-debuginfo-0:3.10.0-1160.el7.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-debuginfo-common-ppc64-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-debuginfo-common-ppc64le-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-debuginfo-common-s390x-0:3.10.0-1160.el7.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-debuginfo-common-x86_64-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-devel-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-devel-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-devel-0:3.10.0-1160.el7.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-devel-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-doc-0:3.10.0-1160.el7.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-kdump-0:3.10.0-1160.el7.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-kdump-debuginfo-0:3.10.0-1160.el7.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-kdump-devel-0:3.10.0-1160.el7.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-tools-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-tools-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-tools-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-tools-debuginfo-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-tools-debuginfo-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-tools-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-tools-libs-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-tools-libs-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:kernel-tools-libs-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:perf-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:perf-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:perf-0:3.10.0-1160.el7.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:perf-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:perf-debuginfo-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:perf-debuginfo-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:perf-debuginfo-0:3.10.0-1160.el7.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:perf-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:python-perf-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:python-perf-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:python-perf-0:3.10.0-1160.el7.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:python-perf-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:python-perf-debuginfo-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:python-perf-debuginfo-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:python-perf-debuginfo-0:3.10.0-1160.el7.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-7.9:python-perf-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:bpftool-debuginfo-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:bpftool-debuginfo-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:bpftool-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:kernel-debug-debuginfo-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:kernel-debug-debuginfo-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:kernel-debug-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:kernel-debug-devel-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:kernel-debuginfo-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:kernel-debuginfo-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:kernel-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:kernel-debuginfo-common-ppc64-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:kernel-debuginfo-common-ppc64le-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:kernel-debuginfo-common-x86_64-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:kernel-tools-debuginfo-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:kernel-tools-debuginfo-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:kernel-tools-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:kernel-tools-libs-devel-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:kernel-tools-libs-devel-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:kernel-tools-libs-devel-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:perf-debuginfo-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:perf-debuginfo-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:perf-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:python-perf-debuginfo-0:3.10.0-1160.el7.ppc64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:python-perf-debuginfo-0:3.10.0-1160.el7.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Server-optional-7.9:python-perf-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-7.9:bpftool-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-7.9:bpftool-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-7.9:kernel-0:3.10.0-1160.el7.src | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-7.9:kernel-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-7.9:kernel-abi-whitelists-0:3.10.0-1160.el7.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-7.9:kernel-debug-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-7.9:kernel-debug-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-7.9:kernel-debug-devel-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-7.9:kernel-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-7.9:kernel-debuginfo-common-x86_64-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-7.9:kernel-devel-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-7.9:kernel-doc-0:3.10.0-1160.el7.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-7.9:kernel-tools-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-7.9:kernel-tools-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-7.9:kernel-tools-libs-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-7.9:perf-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-7.9:perf-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-7.9:python-perf-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-7.9:python-perf-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-optional-7.9:bpftool-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-optional-7.9:kernel-debug-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-optional-7.9:kernel-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-optional-7.9:kernel-debuginfo-common-x86_64-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-optional-7.9:kernel-tools-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-optional-7.9:kernel-tools-libs-devel-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-optional-7.9:perf-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: 7Workstation-optional-7.9:python-perf-debuginfo-0:3.10.0-1160.el7.x86_64 | — |
Vendor Fix
fix
Workaround
|
A flaw was found in the Linux kernel’s implementation of the SAS expander subsystem, where a race condition exists in the smp_task_timedout() and smp_task_done() in drivers/scsi/libsas/sas_expander.c. An attacker could abuse this flaw to corrupt memory and escalate privileges.
An out-of-bounds write flaw was found in the i2c driver in the Linux kernel. This flaw allows an attacker to escalate privileges with system execution privileges. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.
A flaw was found in the Linux kernel's video driver. A race condition, leading to a use-after-free, could lead to a local privilege escalation. User interaction is not needed for exploitation.
A flaw was found in the way Linux kernel's Dynamic Logical Partitioning (DLPAR) functionality on PowerPC systems handled low memory conditions on device discovery. An attacker who can change the LPAR configuration and incur low memory conditions at the same time could use this flaw to crash the system.
A vulnerability was found in the Linux kernel. The Zr364xx USB device driver is susceptible to malicious USB devices. An attacker able to add a specific USB device could cause a crash leading to a denial of service.
A memory leak flaw was found in the Linux kernel. An error in the resource cleanup of the sas_ex_discover_expander function can allow an attacker to induce error conditions that could crash the system. The highest threat from this vulnerability is to system availability.
A flaw was found in the Linux kernel's implementation of the HCI UART driver. A local attacker with access permissions to the Bluetooth device can issue an ioctl, which triggers the hci_uart_set_proto() function in drivers/bluetooth/hci_ldisc.c. The flaw in this function can cause memory corruption or a denial of service because of a use-after-free issue when the hci_uart_register_dev() fails.
A flaw was found in the Linux kernel. A NULL pointer dereference flaw was found in the FUJITSU Extended Socket Network driver. A call to the alloc_workqueue return was not validated and causes a denial of service at the time of failure. The highest threat from this vulnerability is to system availability.
A flaw was found in the Linux kernel. A NULL pointer dereference flaw was found in the QLOGIC drivers for HBA. A call to alloc_workqueue return was not validated and can cause a denial of service. The highest threat from this vulnerability is to system availability.
A flaw was found in the way the sit_init_net function in the Linux kernel handled resource cleanup on errors. This flaw allows an attacker to use the error conditions to crash the system.
A vulnerability was discovered in the Linux kernel's AF_IEEE802154 networking module where permissions checks are not enforced. This can allow an unprivileged user to create raw sockets for this protocol leading to the potential for data leaks or system unavailability.
A vulnerability was found in the Linux kernel’s implementation of the AF_ISDN protocol, which does not enforce the CAP_NET_RAW capability. This flaw can allow unprivileged users to create a raw socket for this protocol. This could further allow the user to control the availability of an existing ISDN circuit.
A flaw was found in the AMD Cryptographic Co-processor driver in the Linux kernel. An attacker, able to send invalid SHA type commands, could cause the system to crash. The highest threat from this vulnerability is to system availability.
A memory leak problem was found in __ipmi_bmc_register in drivers/char/ipmi/ipmi_msghandler.c in Intelligent Platform Management Interface (IPMI) which is used for incoming and outgoing message routing purpose. This flaw may allow an attacker with minimal privilege to cause a denial of service by triggering ida_simple_get() failure.
A flaw was found in the Linux kernel. The Wireless configuration API functionality mishandles resource cleanup in nl80211_get_ftm_responder_stats function. An attacker able to trigger the resource cleanup code path could use this flaw to crash the system. The highest threat from this vulnerability is to system availability.
A flaw was found in the Linux kernel. The Intel Wireless WiFi MVM Firmware driver mishandles resource cleanup during device coredump. An attacker able to trigger the device coredump and system-wide out of memory conditions at the same time could use this flaw to crash the system. The highest threat from this vulnerability is to system availability.
A flaw was found in the way the Intel Wireless driver in the Linux kernel handled resource cleanup during Gen 3 device initialization. This flaw allows an attacker with the ability to restrict access to DMA coherent memory on device initialization, to crash the system.
A flaw was found in the Linux kernel. The crypto_report function mishandles resource cleanup on error. A local attacker able to induce the error conditions could use this flaw to crash the system. The highest threat from this vulnerability is to system availability.
A flaw was found in the Linux kernel. The rtl_usb_probe function mishandles resource cleanup on error. An attacker able to induce the error conditions could use this flaw to crash the system. The highest threat from this vulnerability is to system availability.
An out-of-bounds memory write issue was found in the way the Linux kernel's KVM hypervisor handled the 'KVM_GET_EMULATED_CPUID' ioctl(2) request to get CPUID features emulated by the KVM hypervisor. A user or process able to access the '/dev/kvm' device could use this flaw to crash the system, resulting in a denial of service.
A flaw was found in the Linux kernel's ext4_unlink function. An attacker could corrupt memory or escalate privileges when deleting a file from a recently unmounted specially crafted ext4 filesystem, including local, USB, and iSCSI.
A flaw was found in the Linux kernel’s implementation for ADU devices from Ontrak Control Systems, where an attacker with administrative privileges and access to a local account could pre-groom the memory and physically disconnect or unload a module. The attacker must be able to access either of these two events to trigger the use-after-free, and then race the access to the use-after-free, to create a situation where key USB structs can be manipulated into corrupting memory.
A use-after-free flaw was found in the Linux kernel’s input device driver functionality when unplugging a device. A user with physical access could use this flaw to crash the system.
A use-after-free flaw was found in the acm_probe USB subsystem in the Linux kernel. A race condition occurs when a destroy() procedure is initiated allowing the refcount to decrement on the interface so early that it is never under counted. A malicious USB device is required for exploit. System availability is the largest threat from the vulnerability, however data integrity and confidentiality are also threatened.
An information-leak flaw was found in the Linux kernel's pcan USB driver. When a device using this driver connects to the system, the stack information is leaked to the CAN bus, a controller area network for automobiles. The highest threat with this vulnerability is breach of data confidentiality.
A flaw was found in the Linux kernel, where there is a race condition bug that can be caused by a malicious USB device in the USB character device driver layer. An attacker who can hotplug at least two devices of this class can cause a use-after-free situation.
A use-after-free flaw was found in the Linux kernel’s ext4 file system functionality when the user mount ext4 partition, with the usage of an additional debug parameter is defining an extra inode size. If this parameter has a non zero value, this flaw allows a local user to crash the system when inode expansion happens.
A memory flaw was found in the ALSA subsystem of the Linux kernel. The struct snd_timer_instance function fails the timer->max_instances check leading to an invalid address. This could lead to a use-after-free vulnerability.
A flaw was found in the Linux kernel’s implementation of dropping sysctl entries. A local attacker who has access to load modules on the system can trigger a condition during module load failure and panic the system.
A flaw was found in the Linux kernel's mwifiex driver implementation when connecting to other WiFi devices in "Test Mode." A kernel memory leak can occur if an error condition is met during the parameter negotiation. This issue can lead to a denial of service if multiple error conditions meeting the repeated connection attempts are attempted.
An out-of-bounds write flaw was found in the Linux kernel. A crafted keycode table could be used by drivers/input/input.c to perform the out-of-bounds write. A local user with root access can insert garbage to this keycode table that can lead to out-of-bounds memory access. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.
A flaw was found in the Linux kernel's implementation of some networking protocols in IPsec, such as VXLAN and GENEVE tunnels over IPv6. When an encrypted tunnel is created between two hosts, the kernel isn't correctly routing tunneled data over the encrypted link; rather sending the data unencrypted. This would allow anyone in between the two endpoints to read the traffic unencrypted. The main threat from this vulnerability is to data confidentiality.
A flaw was found in the way KVM hypervisor handled instruction emulation for the L2 guest when nested(=1) virtualization is enabled. In the instruction emulation, the L2 guest could trick the L0 hypervisor into accessing sensitive bits of the L1 hypervisor. An L2 guest could use this flaw to potentially access information of the L1 hypervisor.
A flaw was found in the Linux kernel’s virtual console resize functionality. An attacker with local access to virtual consoles can use the virtual console resizing code to gather kernel internal data structures.
A flaw was found in the Linux kernel’s implementation of the invert video code on VGA consoles when a local attacker attempts to resize the console. An out-of-bounds read can occur, leaking information to the console.
An out-of-bounds (OOB) memory access flaw was found in the floppy driver module in the Linux kernel. A bounds check failure allows a local attacker to gain access to out-of-bounds memory leading to a system crash or a leak of internal kernel information. The highest threat from this vulnerability is to system availability.
There is a use-after-free problem seen due to a race condition between the release of ptp_clock and cdev while resource deallocation. When a (high privileged) process allocates a ptp device file (like /dev/ptpX) and voluntarily goes to sleep. During this time if the underlying device is removed, it can cause an exploitable condition as the process wakes up to terminate and clean all attached files. The system crashes due to the cdev structure being invalid (as already freed) which is pointed to by the inode.
A flaw was found in the Linux kernel’s implementation of Userspace core dumps. This flaw allows an attacker with a local account to crash a trivial program and exfiltrate private kernel data.
CWE-908 - Use of Uninitialized ResourceA flaw was found in the Linux kernel. An index buffer overflow during Direct IO write leading to the NFS client to crash. In some cases, a reach out of the index after one memory allocation by kmalloc will cause a kernel panic. The highest threat from this vulnerability is to data confidentiality and system availability.
A flaw was found in the Linux kernel’s SELinux LSM hook implementation, where it anticipated the skb would only contain a single Netlink message. The hook incorrectly validated the first Netlink message in the skb only, to allow or deny the rest of the messages within the skb with the granted permissions and without further processing. At this time, there is no known ability for an attacker to abuse this flaw.
A stack buffer overflow issue was found in the get_raw_socket() routine of the Host kernel accelerator for virtio net (vhost-net) driver. It could occur while doing an ictol(VHOST_NET_SET_BACKEND) call, and retrieving socket name in a kernel stack variable via get_raw_socket(). A user able to perform ioctl(2) calls on the '/dev/vhost-net' device may use this flaw to crash the kernel resulting in DoS issue.
An out-of-bounds write flaw was found in the Linux kernel. An empty nodelist in mempolicy.c is mishandled durig mount option parsing leading to a stack-based out-of-bounds write. The highest threat from this vulnerability is to system availability.
A vulnerability was found in sg_write in drivers/scsi/sg.c in the SCSI generic (sg) driver subsystem. This flaw allows an attacker with local access and special user or root privileges to cause a denial of service if the allocated list is not cleaned with an invalid (Sg_fd * sfp) pointer at the time of failure, also possibly causing a kernel internal information leak problem.
A flaw was found in the Linux kernel loose validation of child/parent process identification handling while filtering signal handlers. A local attacker is able to abuse this flaw to bypass checks to send any signal to a privileged process.
An out-of-bounds memory write flaw was found in how the Linux kernel’s Voice Over IP H.323 connection tracking functionality handled connections on ipv6 port 1720. This flaw allows an unauthenticated remote user to crash the system, causing a denial of service. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.
Loading 2.4 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.