RHSA-2026:77216
Vulnerability from csaf_redhat - Published: 2026-10-07 03:10 - Updated: 2026-11-20 11:06A flaw was found in the Linux kernel's ALSA (Advanced Linux Sound Architecture) firewire-motu driver. This vulnerability may result in a Denial of Service (DoS) or memory corruption. A local user with access to the device interface can trigger an out-of-bounds write by providing a buffer smaller than the expected header size during event handling.
| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:bpftool-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:bpftool-debuginfo-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-0:4.18.0-372.220.1.el8_6.src | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-abi-stablelists-0:4.18.0-372.220.1.el8_6.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-core-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-debug-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-debug-core-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-debug-debuginfo-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-debug-devel-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-debug-modules-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-debug-modules-extra-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-debuginfo-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-debuginfo-common-x86_64-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-devel-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-doc-0:4.18.0-372.220.1.el8_6.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-modules-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-modules-extra-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-tools-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-tools-debuginfo-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:kernel-tools-libs-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:perf-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:perf-debuginfo-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:python3-perf-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.AUS:python3-perf-debuginfo-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:bpftool-0:4.18.0-372.220.1.el8_6.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:bpftool-0:4.18.0-372.220.1.el8_6.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:bpftool-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:bpftool-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:bpftool-debuginfo-0:4.18.0-372.220.1.el8_6.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:bpftool-debuginfo-0:4.18.0-372.220.1.el8_6.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:bpftool-debuginfo-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:bpftool-debuginfo-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-0:4.18.0-372.220.1.el8_6.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-0:4.18.0-372.220.1.el8_6.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-0:4.18.0-372.220.1.el8_6.src | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-abi-stablelists-0:4.18.0-372.220.1.el8_6.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-core-0:4.18.0-372.220.1.el8_6.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-core-0:4.18.0-372.220.1.el8_6.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-core-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-core-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debug-0:4.18.0-372.220.1.el8_6.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debug-0:4.18.0-372.220.1.el8_6.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debug-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debug-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debug-core-0:4.18.0-372.220.1.el8_6.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debug-core-0:4.18.0-372.220.1.el8_6.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debug-core-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debug-core-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debug-debuginfo-0:4.18.0-372.220.1.el8_6.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debug-debuginfo-0:4.18.0-372.220.1.el8_6.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debug-debuginfo-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debug-debuginfo-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debug-devel-0:4.18.0-372.220.1.el8_6.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debug-devel-0:4.18.0-372.220.1.el8_6.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debug-devel-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debug-devel-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debug-modules-0:4.18.0-372.220.1.el8_6.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debug-modules-0:4.18.0-372.220.1.el8_6.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debug-modules-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debug-modules-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debug-modules-extra-0:4.18.0-372.220.1.el8_6.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debug-modules-extra-0:4.18.0-372.220.1.el8_6.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debug-modules-extra-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debug-modules-extra-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debuginfo-0:4.18.0-372.220.1.el8_6.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debuginfo-0:4.18.0-372.220.1.el8_6.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debuginfo-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debuginfo-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debuginfo-common-aarch64-0:4.18.0-372.220.1.el8_6.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debuginfo-common-ppc64le-0:4.18.0-372.220.1.el8_6.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debuginfo-common-s390x-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-debuginfo-common-x86_64-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-devel-0:4.18.0-372.220.1.el8_6.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-devel-0:4.18.0-372.220.1.el8_6.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-devel-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-devel-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-doc-0:4.18.0-372.220.1.el8_6.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-modules-0:4.18.0-372.220.1.el8_6.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-modules-0:4.18.0-372.220.1.el8_6.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-modules-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-modules-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-modules-extra-0:4.18.0-372.220.1.el8_6.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-modules-extra-0:4.18.0-372.220.1.el8_6.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-modules-extra-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-modules-extra-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-tools-0:4.18.0-372.220.1.el8_6.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-tools-0:4.18.0-372.220.1.el8_6.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-tools-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-tools-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-tools-debuginfo-0:4.18.0-372.220.1.el8_6.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-tools-debuginfo-0:4.18.0-372.220.1.el8_6.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-tools-debuginfo-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-tools-debuginfo-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-tools-libs-0:4.18.0-372.220.1.el8_6.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-tools-libs-0:4.18.0-372.220.1.el8_6.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-tools-libs-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-zfcpdump-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-zfcpdump-core-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-zfcpdump-debuginfo-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-zfcpdump-devel-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-zfcpdump-modules-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:kernel-zfcpdump-modules-extra-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:perf-0:4.18.0-372.220.1.el8_6.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:perf-0:4.18.0-372.220.1.el8_6.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:perf-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:perf-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:perf-debuginfo-0:4.18.0-372.220.1.el8_6.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:perf-debuginfo-0:4.18.0-372.220.1.el8_6.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:perf-debuginfo-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:perf-debuginfo-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:python3-perf-0:4.18.0-372.220.1.el8_6.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:python3-perf-0:4.18.0-372.220.1.el8_6.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:python3-perf-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:python3-perf-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:python3-perf-debuginfo-0:4.18.0-372.220.1.el8_6.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:python3-perf-debuginfo-0:4.18.0-372.220.1.el8_6.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:python3-perf-debuginfo-0:4.18.0-372.220.1.el8_6.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-8.6.0.Z.EUS.EXTENSION:python3-perf-debuginfo-0:4.18.0-372.220.1.el8_6.x86_64 | — |
Vendor Fix
fix
|
A flaw was found in the Linux kernel's `xfrm` (IP eXtensible FRamework) subsystem. This vulnerability involves a race condition where a network device's reference is released too early during packet processing after asynchronous cryptography. This premature release can lead to the system attempting to access a deallocated device, potentially causing a system crash (Denial of Service).
A flaw was found in the Linux kernel's Universal Disk Format (UDF) filesystem. A remote attacker could exploit this vulnerability by tricking a user into mounting a specially crafted UDF image containing repeated partition descriptors. This could lead to a heap out-of-bounds write, potentially causing system instability, denial of service, or arbitrary code execution.
A flaw was found in the Linux kernel's RDMA/rxe component. The `rxe_rcv()` function does not adequately validate the BTH pad and ICRC fields of incoming packets before calculating the payload size. A remote attacker could exploit this by sending a specially crafted short packet or a packet with a forged BTH pad. This could lead to an integer underflow, potentially causing unexpected behavior or a denial of service in the receive path.
A flaw was found in the Linux kernel's Soft RoCE (RDMA/rxe) driver. An unauthenticated remote attacker can send a specially crafted UDP packet with an unknown opcode to trigger an out-of-bounds read. This vulnerability can lead to a kernel panic, effectively causing a Denial of Service (DoS) on the affected system. The issue arises from insufficient validation of unknown opcodes before performing length arithmetic during Cyclic Redundancy Check (CRC) processing.
A flaw was found in the Linux kernel. The `ipc_idr_alloc()` function, used in the checkpoint/restore path for SysV Inter-Process Communication (IPC) ID allocation, does not properly limit ID allocation to the valid range. This can result in the system attempting to dereference freed memory, leading to a use-after-free vulnerability. This issue could potentially cause system instability or information disclosure.
A flaw was found in the Linux kernel's Stream Control Transmission Protocol (SCTP) implementation. This vulnerability, a use-after-free, occurs when the system processes a Stale Cookie ERROR during the setup or reconfiguration of an SCTP association. A remote attacker could exploit this by sending specially crafted SCTP packets. This could lead to a system crash, causing a Denial of Service (DoS).
A flaw was found in the Linux kernel's device-mapper (dm) cache policy, specifically within the smq module. In passthrough mode, the invalidate_mapping operation lacks proper locking, allowing for concurrent access. This can lead to data races, resulting in data corruption or use-after-free issues, which may cause system instability or a denial of service.
A flaw was found in the Linux kernel. A race condition exists in the `xfrm` policy handling, specifically within the `xfrm_policy_bysel_ctx()` function. This flaw allows for a use-after-free vulnerability, where memory is accessed after it has been released. This can lead to system instability or a denial of service (DoS), making the system unresponsive or causing it to crash.
A flaw was found in the Linux kernel's IPv6 Virtual Tunnel Interface (vti6) component. An unprivileged local user, particularly within a user namespace, could exploit a vulnerability related to incorrect network namespace handling during the movement of a vti6 tunnel. This issue can lead to a kernel bug, resulting in a denial of service (system crash) and potentially impacting container isolation on affected hosts.
A flaw was found in the Linux kernel's xfrm input component. The transport-mode reinjection process, which handles network packet re-injection, stores a network namespace pointer that must remain valid until a deferred callback completes. However, a missing reference count for the network namespace during this deferred operation could lead to a use-after-free vulnerability. This could allow an attacker to potentially cause a system crash or other unpredictable behavior if the network namespace is deallocated prematurely.
A flaw was found in the Linux kernel's IPv6 Virtual Tunnel Interface (VTI) module. When a VTI tunnel device is moved to a different network environment, an unprivileged user in a separate user space can manipulate tunnel parameters. This manipulation could allow the user to intercept or redirect network traffic intended for other parts of the system or other containers, leading to unauthorized information disclosure or denial of service across different tenants on a container host.
A flaw was found in the Linux kernel's netfilter synproxy module. When handling TCP timestamp options, a stale pointer can be used after memory reallocation. This can result in memory corruption, where data is written to a freed memory area, or lead to packets being sent with an incorrect checksum. A remote attacker could potentially exploit this to cause system instability or network communication issues.
A flaw was found in the Linux kernel's nvmet subsystem. An unauthenticated remote attacker could exploit an out-of-bounds heap read vulnerability in the Discovery Get Log Page function. By sending a specially crafted request with a manipulated offset, an attacker could read sensitive kernel memory, leading to information disclosure of kernel pointers. This vulnerability could also cause a denial of service by crashing the target host.
A flaw was found in the Linux kernel's RDMA/rxe component. A race condition in the `rxe_mmap()` function, which manages memory for Remote Direct Memory Access (RDMA) operations, can lead to a use-after-free vulnerability. A local attacker could exploit this timing issue to cause a system crash, resulting in a denial of service. In some scenarios, this could also potentially lead to a page-level use-after-free, which might allow for further system compromise.
A flaw was found in the Linux kernel's QRTR (Qualcomm IPC Router) networking component. An unprivileged local attacker can create a QRTR socket in a separate network namespace. Due to improper handling of global state variables, this allows the attacker to send datagrams and control-plane messages to QRTR sockets in other network namespaces. This bypasses network namespace isolation, enabling unauthorized communication and potential information disclosure between isolated network environments.
A flaw was found in the Linux kernel's `xfrm` subsystem. This vulnerability arises when asynchronous cryptographic operations incorrectly handle network packet segments, leaving a pointer to memory that has already been released. An attacker could potentially exploit this use-after-free condition to cause a system crash (denial of service) or, in some scenarios, execute unauthorized code.
An attacker executing code on affected system could inject an interrupt at a precise moment to disrupt "Safe RET", the default Linux mitigation for speculative Return Overflow (SRSO), which could potentially weaken that protection and may result in information disclosure.
A flaw was found in the Linux kernel's `libiscsi_tcp` component. A remote attacker, acting as a malicious iSCSI target, could send a specially crafted iSCSI SCSI Command Response (ISCSI_OP_SCSI_CMD_RSP) with an oversized data segment. This could lead to a buffer overflow in a fixed-size buffer, potentially causing memory corruption within the kernel.
A flaw was found in the netfilter flowtable component of the Linux kernel. This vulnerability occurs due to a timing issue where the system's garbage collection can free a network flow while it is still being set up. This can lead to a 'use-after-free' condition, where the system attempts to access memory that has already been released. This memory corruption could potentially result in a system crash (denial of service) or, in certain circumstances, allow for arbitrary code execution.
A flaw was found in the Linux kernel's RDMA/rxe component. A local user could exploit a memory corruption vulnerability in the `free_rd_atomic_resources()` function by updating the `max_dest_rd_atomic` value before the old array is properly freed, leading to an out-of-bounds write. This issue can cause a system crash, resulting in a denial of service (DoS).
A flaw was found in the Linux kernel's Remote Direct Memory Access (RDMA) subsystem, specifically within the rxe component. A local, unprivileged user could exploit a race condition during a queue pair modification operation. This could lead to a use-after-free vulnerability, allowing the attacker to cause a system crash and resulting in a Denial of Service (DoS).
Loading 1.1 MB of JSON…
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
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.