RHSA-2024:5281
Vulnerability from csaf_redhat - Published: 2024-08-13 15:09 - Updated: 2026-09-01 11:55A vulnerability was found in the Linux kernel's Qualcomm EMAC driver, where the emac_remove function can lead to a use-after-free issue when the driver tries to access data after the network device has been freed, causing instability and a crash in the network subsystem.
| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:bpftool-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:bpftool-debuginfo-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-0:4.18.0-372.118.1.el8_6.src | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-abi-stablelists-0:4.18.0-372.118.1.el8_6.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-core-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-debug-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-debug-core-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-debug-debuginfo-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-debug-devel-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-debug-modules-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-debug-modules-extra-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-debuginfo-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-debuginfo-common-x86_64-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-devel-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-doc-0:4.18.0-372.118.1.el8_6.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-modules-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-modules-extra-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-tools-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-tools-debuginfo-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-tools-libs-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:perf-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:perf-debuginfo-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:python3-perf-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:python3-perf-debuginfo-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:bpftool-0:4.18.0-372.118.1.el8_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:bpftool-0:4.18.0-372.118.1.el8_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:bpftool-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:bpftool-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:bpftool-debuginfo-0:4.18.0-372.118.1.el8_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:bpftool-debuginfo-0:4.18.0-372.118.1.el8_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:bpftool-debuginfo-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:bpftool-debuginfo-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-0:4.18.0-372.118.1.el8_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-0:4.18.0-372.118.1.el8_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-0:4.18.0-372.118.1.el8_6.src | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-abi-stablelists-0:4.18.0-372.118.1.el8_6.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-core-0:4.18.0-372.118.1.el8_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-core-0:4.18.0-372.118.1.el8_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-core-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-core-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debug-0:4.18.0-372.118.1.el8_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debug-0:4.18.0-372.118.1.el8_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debug-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debug-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debug-core-0:4.18.0-372.118.1.el8_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debug-core-0:4.18.0-372.118.1.el8_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debug-core-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debug-core-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debug-debuginfo-0:4.18.0-372.118.1.el8_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debug-debuginfo-0:4.18.0-372.118.1.el8_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debug-debuginfo-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debug-debuginfo-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debug-devel-0:4.18.0-372.118.1.el8_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debug-devel-0:4.18.0-372.118.1.el8_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debug-devel-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debug-devel-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debug-modules-0:4.18.0-372.118.1.el8_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debug-modules-0:4.18.0-372.118.1.el8_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debug-modules-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debug-modules-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debug-modules-extra-0:4.18.0-372.118.1.el8_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debug-modules-extra-0:4.18.0-372.118.1.el8_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debug-modules-extra-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debug-modules-extra-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debuginfo-0:4.18.0-372.118.1.el8_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debuginfo-0:4.18.0-372.118.1.el8_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debuginfo-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debuginfo-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debuginfo-common-aarch64-0:4.18.0-372.118.1.el8_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debuginfo-common-ppc64le-0:4.18.0-372.118.1.el8_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debuginfo-common-s390x-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-debuginfo-common-x86_64-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-devel-0:4.18.0-372.118.1.el8_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-devel-0:4.18.0-372.118.1.el8_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-devel-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-devel-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-doc-0:4.18.0-372.118.1.el8_6.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-modules-0:4.18.0-372.118.1.el8_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-modules-0:4.18.0-372.118.1.el8_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-modules-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-modules-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-modules-extra-0:4.18.0-372.118.1.el8_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-modules-extra-0:4.18.0-372.118.1.el8_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-modules-extra-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-modules-extra-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-tools-0:4.18.0-372.118.1.el8_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-tools-0:4.18.0-372.118.1.el8_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-tools-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-tools-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-tools-debuginfo-0:4.18.0-372.118.1.el8_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-tools-debuginfo-0:4.18.0-372.118.1.el8_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-tools-debuginfo-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-tools-debuginfo-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-tools-libs-0:4.18.0-372.118.1.el8_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-tools-libs-0:4.18.0-372.118.1.el8_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-tools-libs-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-zfcpdump-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-zfcpdump-core-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-zfcpdump-debuginfo-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-zfcpdump-devel-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-zfcpdump-modules-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-zfcpdump-modules-extra-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:perf-0:4.18.0-372.118.1.el8_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:perf-0:4.18.0-372.118.1.el8_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:perf-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:perf-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:perf-debuginfo-0:4.18.0-372.118.1.el8_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:perf-debuginfo-0:4.18.0-372.118.1.el8_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:perf-debuginfo-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:perf-debuginfo-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:python3-perf-0:4.18.0-372.118.1.el8_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:python3-perf-0:4.18.0-372.118.1.el8_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:python3-perf-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:python3-perf-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:python3-perf-debuginfo-0:4.18.0-372.118.1.el8_6.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:python3-perf-debuginfo-0:4.18.0-372.118.1.el8_6.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:python3-perf-debuginfo-0:4.18.0-372.118.1.el8_6.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:python3-perf-debuginfo-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:bpftool-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:bpftool-debuginfo-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:kernel-0:4.18.0-372.118.1.el8_6.src | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:kernel-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:kernel-abi-stablelists-0:4.18.0-372.118.1.el8_6.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:kernel-core-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:kernel-debug-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:kernel-debug-core-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:kernel-debug-debuginfo-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:kernel-debug-devel-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:kernel-debug-modules-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:kernel-debug-modules-extra-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:kernel-debuginfo-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:kernel-debuginfo-common-x86_64-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:kernel-devel-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:kernel-doc-0:4.18.0-372.118.1.el8_6.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:kernel-modules-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:kernel-modules-extra-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:kernel-tools-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:kernel-tools-debuginfo-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:kernel-tools-libs-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:perf-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:perf-debuginfo-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:python3-perf-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:python3-perf-debuginfo-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Vendor Fix
fix
Workaround
|
| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-cross-headers-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-headers-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-cross-headers-0:4.18.0-372.118.1.el8_6.aarch64 | — |
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-cross-headers-0:4.18.0-372.118.1.el8_6.ppc64le | — |
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-cross-headers-0:4.18.0-372.118.1.el8_6.s390x | — |
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-cross-headers-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-headers-0:4.18.0-372.118.1.el8_6.aarch64 | — |
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-headers-0:4.18.0-372.118.1.el8_6.ppc64le | — |
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-headers-0:4.18.0-372.118.1.el8_6.s390x | — |
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.E4S:kernel-headers-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:kernel-cross-headers-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Workaround
|
|
| Unresolved product id: BaseOS-8.6.0.Z.TUS:kernel-headers-0:4.18.0-372.118.1.el8_6.x86_64 | — |
Workaround
|
A vulnerability was found in the Linux kernel's hwmon driver for the w83792d module where a NULL pointer dereference was caused by the lm75[] obsolete structure field. During specific device read operations, if certain conditions are met, the driver may attempt to access a NULL pointer because this unnecessary field is being retained, which can lead to system crashes or instability.
In the Linux kernel, the following vulnerability has been resolved: proc/vmcore: fix clearing user buffer by properly using clear_user() To clear a user buffer we cannot simply use memset, we have to use clear_user(). With a virtio-mem device that registers a vmcore_cb and has some logically unplugged memory inside an added Linux memory block, I can easily trigger a BUG by copying the vmcore via "cp": systemd[1]: Starting Kdump Vmcore Save Service... kdump[420]: Kdump is using the default log level(3). kdump[453]: saving to /sysroot/var/crash/127.0.0.1-2021-11-11-14:59:22/ kdump[458]: saving vmcore-dmesg.txt to /sysroot/var/crash/127.0.0.1-2021-11-11-14:59:22/ kdump[465]: saving vmcore-dmesg.txt complete kdump[467]: saving vmcore BUG: unable to handle page fault for address: 00007f2374e01000 #PF: supervisor write access in kernel mode #PF: error_code(0x0003) - permissions violation PGD 7a523067 P4D 7a523067 PUD 7a528067 PMD 7a525067 PTE 800000007048f867 Oops: 0003 [#1] PREEMPT SMP NOPTI CPU: 0 PID: 468 Comm: cp Not tainted 5.15.0+ #6 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.14.0-27-g64f37cc530f1-prebuilt.qemu.org 04/01/2014 RIP: 0010:read_from_oldmem.part.0.cold+0x1d/0x86 Code: ff ff ff e8 05 ff fe ff e9 b9 e9 7f ff 48 89 de 48 c7 c7 38 3b 60 82 e8 f1 fe fe ff 83 fd 08 72 3c 49 8d 7d 08 4c 89 e9 89 e8 <49> c7 45 00 00 00 00 00 49 c7 44 05 f8 00 00 00 00 48 83 e7 f81 RSP: 0018:ffffc9000073be08 EFLAGS: 00010212 RAX: 0000000000001000 RBX: 00000000002fd000 RCX: 00007f2374e01000 RDX: 0000000000000001 RSI: 00000000ffffdfff RDI: 00007f2374e01008 RBP: 0000000000001000 R08: 0000000000000000 R09: ffffc9000073bc50 R10: ffffc9000073bc48 R11: ffffffff829461a8 R12: 000000000000f000 R13: 00007f2374e01000 R14: 0000000000000000 R15: ffff88807bd421e8 FS: 00007f2374e12140(0000) GS:ffff88807f000000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f2374e01000 CR3: 000000007a4aa000 CR4: 0000000000350eb0 Call Trace: read_vmcore+0x236/0x2c0 proc_reg_read+0x55/0xa0 vfs_read+0x95/0x190 ksys_read+0x4f/0xc0 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae Some x86-64 CPUs have a CPU feature called "Supervisor Mode Access Prevention (SMAP)", which is used to detect wrong access from the kernel to user buffers like this: SMAP triggers a permissions violation on wrong access. In the x86-64 variant of clear_user(), SMAP is properly handled via clac()+stac(). To fix, properly use clear_user() when we're dealing with a user buffer.
A possible use-after-free after handing over to PTP worker was found in the Linux kernel. This may lead to a crash.
A vulnerability was found in the Linux kernel's NFSD, where improper handling of read requests near the maximum offset can lead to an integer overflow. When a client attempts to read from a near-maximum offset, it causes the server to return an invalid NFS error, resulting in indefinite retries by the client. This behavior can disrupt file access and stability in networked environments.
A vulnerability was found in the Linux kernel's NFSD, where an underflow in the ia_size field can occur due to incorrect handling of file size types. When an NFS client sends a file size greater than the maximum value the system can handle, it can lead to an underflow in the ia_size variable, causing unpredictable behavior. This vulnerability impacts the integrity and reliability of file operations in NFS.
A vulnerability was found in the Linux kernel's NFSD, specifically in the handling of large file sizes during NFSv3 SETATTR and CREATE operations. The ia_size field, being a signed 64-bit type, can lead to unexpected behavior when clients send size values larger than the maximum allowed. This improper handling can result in silent value capping, potentially leading to data corruption in file size management.
A flaw was found in the Linux kernel’s uio subsystem. A use-after-free memory flaw in the uio_open functionality allows a local user to crash or escalate their privileges on the system.
A NULL pointer dereference flaw was found in the Linux kernel when accessing the rgd->rd_rgl in the gfs2_rgrp_dump() function. This issue may lead to a crash.
A flaw was found in the Linux kernel. Two TCP spoofing primitives exist where an attacker can brute force the server-chosen send window by acknowledging data that was never sent, called "ghost ACKs." There are side channels that also allow the attacker to leak the otherwise secret server-chosen initial sequence number (ISN). One of these side channels leverages TCP SYN cookies.
A vulnerability was found in the Linux kernel's SUNRPC implementation in the svc_tcp_listen_data_ready() function, where the use-after-free vulnerability occurs when a listener socket is freed while a child socket retains a reference to it, leading to potential access of invalid memory.
Hardware logic with insecure de-synchronization in Intel(R) DSA and Intel(R) IAA for some Intel(R) 4th or 5th generation Xeon(R) processors may allow an authorized user to potentially enable escalation of privilege local access
CVE-2024-35852 addresses a memory leak in the Linux kernel's mlxsw driver, specifically within the Spectrum ACL TCAM module. The issue occurs when rehash work is canceled while pending, leading to allocated hints not being freed properly. This results in a memory leak that can degrade system performance over time. The problem has been resolved by ensuring that any associated hints are freed when the rehash work is canceled. Users should update their Linux kernel to a version that includes this fix to maintain optimal system performance.
In the Linux kernel, the following vulnerability has been resolved: rtnetlink: Correct nested IFLA_VF_VLAN_LIST attribute validation Each attribute inside a nested IFLA_VF_VLAN_LIST is assumed to be a struct ifla_vf_vlan_info so the size of such attribute needs to be at least of sizeof(struct ifla_vf_vlan_info) which is 14 bytes. The current size validation in do_setvfinfo is against NLA_HDRLEN (4 bytes) which is less than sizeof(struct ifla_vf_vlan_info) so this validation is not enough and a too small attribute might be cast to a struct ifla_vf_vlan_info, this might result in an out of bands read access when accessing the saved (casted) entry in ivvl.
A use-after-free flaw was found in the Linux kernel's network route management. This flaw allows an attacker to alter the behavior of certain network connections.
A vulnerability was found in the Linux kernel's Ionic driver in the ionic_qcq_enable() function, where the issue arises when the driver fails to reset the .poll pointer to NULL after a queue is unregistered via netif_napi_del(), leading to a use-after-free scenario when attempting to enable a previously unregistered NAPI, which result in kernel crashes or invalid opcode errors.
A denial of service (DoS) attack was found in the mlx5 driver in the Linux kernel. A KVM guest VM using virtio-net can crash the host by sending a short packet, for example, size < ETH_HLEN. The packet may traverse through vhost-net, macvtap, and vlan without any validation or drop. When this packet is presented to the mlx5 driver on the host side, the kernel panic happens since mlx5_core assumes the frame size is always >= ETH_HLEN.
A denial of service (DoS) attack was found in the mlx5 driver in the Linux kernel. A KVM guest VM using virtio-net can crash the host by sending a short packet, for example, size < ETH_HLEN. The packet may traverse through vhost-net, macvtap, and vlan without any validation or drop. When this packet is presented to the mlx5 driver on the host side, the kernel panic happens since mlx5_core assumes the frame size is always >= ETH_HLEN.
Loading 1.0 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.