RHSA-2025:21091
Vulnerability from csaf_redhat - Published: 2025-11-12 08:15 - Updated: 2026-11-11 18:45A flaw was found in the Linux kernel ALSA USB audio driver. This vulnerability allows a denial of service via a crafted USB audio device.
| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: AppStream-9.0.0.Z.E4S:bpftool-debuginfo-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:bpftool-debuginfo-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:bpftool-debuginfo-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:bpftool-debuginfo-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-debug-devel-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-debug-devel-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-debug-devel-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-debug-devel-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-debug-devel-matched-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-debug-devel-matched-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-debug-devel-matched-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-debug-devel-matched-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-debuginfo-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-debuginfo-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-debuginfo-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-debuginfo-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-debuginfo-common-aarch64-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-debuginfo-common-ppc64le-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-debuginfo-common-s390x-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-debuginfo-common-x86_64-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-devel-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-devel-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-devel-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-devel-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-devel-matched-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-devel-matched-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-devel-matched-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-devel-matched-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-doc-0:5.14.0-70.153.1.el9_0.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-zfcpdump-debuginfo-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-zfcpdump-devel-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:kernel-zfcpdump-devel-matched-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:perf-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:perf-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:perf-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:perf-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:perf-debuginfo-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:perf-debuginfo-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:perf-debuginfo-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:perf-debuginfo-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.0.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:bpftool-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:bpftool-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:bpftool-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:bpftool-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:bpftool-debuginfo-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:bpftool-debuginfo-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:bpftool-debuginfo-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:bpftool-debuginfo-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-0:5.14.0-70.153.1.el9_0.src | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-abi-stablelists-0:5.14.0-70.153.1.el9_0.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-core-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-core-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-core-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-core-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debug-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debug-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debug-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debug-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debug-core-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debug-core-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debug-core-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debug-core-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debug-modules-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debug-modules-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debug-modules-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debug-modules-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debug-modules-extra-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debug-modules-extra-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debug-modules-extra-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debug-modules-extra-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debuginfo-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debuginfo-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debuginfo-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debuginfo-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debuginfo-common-aarch64-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debuginfo-common-ppc64le-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debuginfo-common-s390x-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-debuginfo-common-x86_64-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-modules-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-modules-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-modules-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-modules-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-modules-extra-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-modules-extra-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-modules-extra-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-modules-extra-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-tools-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-tools-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-tools-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-tools-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-tools-libs-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-tools-libs-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-tools-libs-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-zfcpdump-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-zfcpdump-core-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-zfcpdump-debuginfo-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-zfcpdump-modules-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:kernel-zfcpdump-modules-extra-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:perf-debuginfo-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:perf-debuginfo-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:perf-debuginfo-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:perf-debuginfo-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:python3-perf-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:python3-perf-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:python3-perf-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:python3-perf-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-70.153.1.el9_0.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-70.153.1.el9_0.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-70.153.1.el9_0.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.0.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-70.153.1.el9_0.x86_64 | — |
Vendor Fix
fix
|
A null pointer dereference exists in the linux kernel, such that when sfb_init() fails qdisc is NULL, and it will cause gpf issue, leading to damage to the availability of the system.
A flaw was found in the Linux kernel's NILFS2 file system. A local user can cause a Denial of Service (DoS) or memory corruption by triggering an allocation failure during file system object initialization. Due to improper cleanup error handling, the kernel attempts to free uninitialized memory, leading to kernel instability and system crashes.
A flaw was found in the Linux kernel's Bluetooth Logical Link Control and Adaptation Protocol (L2CAP) subsystem. This flaw allows an adjacent attacker within Bluetooth radio range to cause a Denial of Service (DoS) through a system crash. A use-after-free vulnerability occurs due to missing reference count checks during concurrent channel creation and teardown operations. By rapidly initiating and closing Bluetooth connections, an attacker can trigger this race condition, causing the kernel to access already freed memory.
A flaw was found in the Linux kernel's iomap subsystem. This flaw allows a local user to cause a Denial of Service (DoS) or memory corruption by performing concurrent file modifications while storage write errors occur. Due to a race condition during background write operations (writeback), the kernel accesses memory page information after releasing its lock. If another task invalidates or reallocates the memory page at that moment, the kernel encounters an invalid pointer, resulting in a system crash.
A use after free exists in the wifi module of the linux kernel in the function brcmf_netdev_start_xmit(),thereby leading to damage to system availability and integrity.
A flaw was found in the Linux kernel. A race condition in the zswap writeback mechanism allows a local user to cause memory corruption and system instability under heavy memory pressure. When a swap slot is reused while writeback is still in progress, stale data is written and subsequently swapped back in, leading to data corruption or a Denial of Service (DoS).
A flaw was found in the Linux kernel's ath9k Wi-Fi driver. An attacker with physical access to plug in a malicious Universal Serial Bus (USB) device, or the ability to attach an emulated USB device to a virtualized system, can send a specially crafted service connection response message. Because the driver fails to prevent modifications to endpoint attributes reserved for internal control communication, this issue can disrupt driver operations and lead to a system crash, resulting in a Denial of Service (DoS).
A flaw was found in the Linux kernel's Broadcom FullMAC wireless driver (brcmfmac). A local attacker with physical access or control over a connected malicious USB device can provide crafted association data that exceeds expected buffer limits. This flaw causes an out-of-bounds memory read, which can lead to a system crash causing a Denial of Service (DoS) or the leakage of sensitive kernel memory.
A flaw out of bounds read in the Linux kernel Marvell mwifiex driver was found in the way user sends malicious Wi-Fi packets. A remote user with Wi-Fi connection could use this flaw to crash the system.
A flaw was found in the Linux kernel's MediaTek MT7921 wireless driver. The driver attempts to access unallocated memory during device firmware response processing. A local attacker with physical or local access to a system using this wireless hardware can trigger an invalid memory access, causing a kernel crash and resulting in a Denial of Service (DoS).
A flaw was found in the Linux kernel's mac80211 wireless subsystem. An attacker within Wi-Fi radio range can exploit this issue by sending a specially crafted IEEE 802.11ah Sub-1 GHz (S1G) action frame of insufficient length. Because the system fails to verify the frame size before parsing the action code, handling the malformed frame can trigger an out-of-bounds read and crash the kernel, resulting in a Denial of Service (DoS).
A flaw was found in the Linux kernel's Bluetooth Logical Link Control and Adaptation Protocol (L2CAP) component. This vulnerability allows an adjacent attacker within Bluetooth radio range to cause a denial of service (DoS) through a system crash or potentially execute arbitrary code. The issue is caused by a use-after-free memory error triggered when the system processes specially crafted Bluetooth Low Energy (LE) command rejection packets.
An out of bounds array vulnerability exists in the linux kernel, such that a missing check on the start field of a PRZ (persistent ram zone) during initialization leads to damage to the availability and integrity of the system.
A flaw was found in the Linux kernel's network packet handling subsystem. When processing network packets using zero-copy segmentation, internal fragment tracking variables can become out of sync during packet fragmentation. A local user can exploit this vulnerability by initiating network transmissions that require zero-copy packet segmentation, causing a null pointer dereference that results in a kernel crash and Denial of Service (DoS).
A flaw was found in the Linux kernel's Bluetooth subsystem. When clearing stored Bluetooth link and security keys, the system accesses memory that has already been freed, resulting in a use-after-free condition. A local user with Bluetooth administrative privileges can exploit this flaw to cause a Denial of Service (DoS) via a kernel crash or potentially access sensitive data from freed memory.
A null pointer dereference exists in the linux kernel such that in obj_stock_flush_required():stock->cached_objcg can be reset between the check and dereference, resulting in damage to the availability of the system.
A flaw use after free in the Linux kernel XTS (XOR Encrypt XOR with ciphertext stealing) crypto Kernel module was found in the way privileges user triggers XTS crypto API in specific way. A local user could use this flaw to crash the system or potentially escalate their privileges on the system.
A flaw was found in the Linux kernel's IPv6 networking subsystem. An improper reference handling issue in the Multicast Listener Discovery (MLD) protocol allows a network device structure to be released prematurely while still in use, resulting in a use-after-free condition. An adjacent attacker on the local network segment can exploit this vulnerability by sending crafted multicast traffic, leading to a kernel crash and Denial of Service (DoS).
A flaw use of uninitialized memory (uncontrolled and invisible by attacker) in the Linux kernel SCTP transport protocol was found in the way user triggers malicious SCTP packets. A remote user could use this flaw to crash the system. The bug actual only for systems where SCTP protocol being enabled and used.
A flaw use after free in the Linux kernel NFS functionality was found in the way connected user sends malicious data to the server. A remote user could use this flaw to crash the system.
A flaw was found in the Linux kernel. This vulnerability can lead to information disclosure and authentication bypass due to a non-constant-time Message Authentication Code (MAC) comparison in the IPv6 Segment Routing implementation. A network attacker could exploit this timing side-channel flaw by measuring variations in processing time to deduce valid cryptographic tags. Successful exploitation could allow the attacker to forge authenticated network traffic.
A flaw out of boundary read in the Linux kernel NFS functionality was found in the way connected user sends malicious data to the server. A remote user could use this flaw to crash the system.
Loading 1.1 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.