RHSA-2026:92993
Vulnerability from csaf_redhat - Published: 2026-10-30 06:37 - Updated: 2026-10-31 08:47A flaw was discovered in the Linux kernel’s AHCI driver subsystem.The driver allocated an array of 8 elements (ahci_em_priv[8]), but under certain SATA Port Multiplier (PMP) configurations, the code in sata_pmp_init_links() could index up to SATA_PMP_MAX_PORTS (which may exceed 8), triggering a potential array-index-out-of-bounds condition. This could result in memory corruption and compromise of system integrity or availability.
| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: AppStream-9.2.0.Z.E4S:bpftool-debuginfo-0:7.0.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:bpftool-debuginfo-0:7.0.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:bpftool-debuginfo-0:7.0.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:bpftool-debuginfo-0:7.0.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-64k-debug-debuginfo-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-64k-debug-devel-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-64k-debug-devel-matched-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-64k-debuginfo-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-64k-devel-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-64k-devel-matched-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-debug-devel-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-debug-devel-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-debug-devel-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-debug-devel-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-debug-devel-matched-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-debug-devel-matched-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-debug-devel-matched-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-debug-devel-matched-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-debuginfo-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-debuginfo-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-debuginfo-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-debuginfo-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-debuginfo-common-aarch64-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-debuginfo-common-ppc64le-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-debuginfo-common-s390x-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-debuginfo-common-x86_64-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-devel-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-devel-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-devel-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-devel-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-devel-matched-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-devel-matched-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-devel-matched-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-devel-matched-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-doc-0:5.14.0-284.200.1.el9_2.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-zfcpdump-debuginfo-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-zfcpdump-devel-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:kernel-zfcpdump-devel-matched-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:perf-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:perf-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:perf-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:perf-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:perf-debuginfo-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:perf-debuginfo-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:perf-debuginfo-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:perf-debuginfo-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:rtla-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:rtla-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:rtla-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.2.0.Z.E4S:rtla-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:bpftool-0:7.0.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:bpftool-0:7.0.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:bpftool-0:7.0.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:bpftool-0:7.0.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:bpftool-debuginfo-0:7.0.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:bpftool-debuginfo-0:7.0.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:bpftool-debuginfo-0:7.0.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:bpftool-debuginfo-0:7.0.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-0:5.14.0-284.200.1.el9_2.src | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-64k-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-64k-core-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-64k-debug-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-64k-debug-core-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-64k-debug-debuginfo-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-64k-debug-modules-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-64k-debug-modules-core-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-64k-debug-modules-extra-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-64k-debuginfo-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-64k-modules-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-64k-modules-core-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-64k-modules-extra-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-abi-stablelists-0:5.14.0-284.200.1.el9_2.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-core-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-core-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-core-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-core-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-core-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-core-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-core-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-core-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-modules-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-modules-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-modules-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-modules-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-modules-core-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-modules-core-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-modules-core-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-modules-core-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-modules-extra-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-modules-extra-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-modules-extra-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-modules-extra-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debug-uki-virt-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debuginfo-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debuginfo-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debuginfo-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debuginfo-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debuginfo-common-aarch64-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debuginfo-common-ppc64le-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debuginfo-common-s390x-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-debuginfo-common-x86_64-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-modules-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-modules-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-modules-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-modules-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-modules-core-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-modules-core-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-modules-core-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-modules-core-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-modules-extra-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-modules-extra-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-modules-extra-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-modules-extra-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-tools-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-tools-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-tools-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-tools-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-tools-libs-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-tools-libs-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-tools-libs-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-uki-virt-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-zfcpdump-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-zfcpdump-core-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-zfcpdump-debuginfo-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-zfcpdump-modules-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-zfcpdump-modules-core-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:kernel-zfcpdump-modules-extra-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:perf-debuginfo-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:perf-debuginfo-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:perf-debuginfo-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:perf-debuginfo-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:python3-perf-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:python3-perf-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:python3-perf-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:python3-perf-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-284.200.1.el9_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-284.200.1.el9_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-284.200.1.el9_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.2.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-284.200.1.el9_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
A flaw was found in the Linux kernel's qla2xxx SCSI driver. This vulnerability occurs when commands sent to the firmware (FW) are not properly cleared after a chip reset. A local attacker could exploit a race condition during direct memory access (DMA) unmapping, leading to a kernel panic. This can result in a system crash and a Denial of Service (DoS).
A flaw was found in the Linux kernel's Bluetooth management (MGMT) component. An attacker could exploit a vulnerability in how Long Term Keys (LTK) are loaded. By providing an oversized encryption size, a stack buffer overflow can occur, potentially leading to a denial of service.
A flaw was found in the Linux kernel's `nfnetlink_cthelper` component. This vulnerability, an out-of-bounds read, occurs in the `nfnl_cthelper_dump_table()` function when a network connection tracking helper is removed during a dump operation, leading to a bypassed bounds check. A local attacker could exploit this to cause a system crash (denial of service) or potentially access sensitive information from kernel memory.
A flaw was found in the Linux kernel's `pcrypt` component. This vulnerability involves how the system handles certain requests, specifically `MAY_BACKLOG` requests, which can indicate a temporary busy state. If not properly managed, the system's processing of these requests could lead to resource exhaustion or instability.
A flaw was found in the Linux kernel's SCSI target subsystem. This vulnerability, a buffer overflow, occurs in the `tg_pt_gp_members_show()` function when processing long iSCSI IQN names. An attacker could potentially exploit this by providing a specially crafted input, leading to the disclosure of sensitive information from the kernel stack or a denial of service (DoS) if `CONFIG_FORTIFY_SOURCE` is enabled.
A flaw was found in the Linux kernel's `af_alg` cryptography module. This vulnerability involves an arithmetic overflow when processing associated data lengths during the transmit buffer size check. A remote attacker could exploit this flaw by providing a specially crafted associated data length, potentially leading to a denial of service (DoS) due to system instability.
A flaw was found in the Linux kernel's Stream Control Transmission Protocol (SCTP) implementation. Specifically, improper validation of embedded INIT chunk and address list lengths in SCTP cookies could allow a remote attacker to trigger out-of-bounds reads. This could lead to information disclosure or potentially a denial of service (DoS) condition.
A flaw was found in the Linux kernel's Stream Control Transmission Protocol (SCTP) implementation. A remote attacker could exploit this by sending a specially crafted COOKIE_ECHO chunk to a listening SCTP server. The server's failure to properly validate the length of a cached peer INIT chunk within the COOKIE_ECHO payload could lead to out-of-bounds reads and memory corruption. This could result in a denial of service or potentially information disclosure.
A flaw was found in the Linux kernel's block input/output control group (blk-cgroup) component. This vulnerability, a Use-After-Free (UAF), occurs when multiple block control groups are released at the same time. A race condition allows one group to remove another's entries while it is still in use, leading to premature memory deallocation. This can result in system instability or a denial of service.
A flaw was found in the Linux kernel's mac802154 (IEEE 802.15.4 MAC security) component. This vulnerability allows for data corruption and potential kernel crashes when cryptographic transformations are performed on shared network packet data without proper isolation. A remote attacker could exploit this by sending specific 802.15.4 traffic, leading to system instability or denial of service.
A flaw was found in the Linux kernel's IPv6 networking stack. An unprivileged local user could exploit a vulnerability in how IPv6 extension header lengths are handled. By manipulating these headers using nftables, an attacker can trigger an out-of-bounds read, leading to information disclosure from kernel memory.
A flaw was found in the Linux kernel's IPv6 extension header processing. When processing the Home Address Option (HAO), the cached network header pointer may become invalid if the packet's memory is reallocated. This can lead to incorrect parsing of subsequent IPv6 Type-Length-Value (TLV) options, potentially causing unexpected network behavior or a denial of service.
A flaw was found in the Linux kernel's handling of IPv6 extended headers. Specifically, the `ipv6_hop_jumbo()` function, which processes jumbo payloads, can modify internal packet buffer (skb) pointers. However, the network header (nh) pointer is not recomputed after these modifications. This oversight could lead to incorrect data processing, potentially causing system instability or a denial of service (DoS) due to malformed packets.
A flaw was found in the Linux kernel's IPv6 Routing Protocol for Low-Power and Lossy Networks (RPL) segment routing header (SRH) decompression function, ipv6_rpl_srh_decompress(). An integer overflow occurs when processing a specially crafted IPv6 packet, causing the header length calculation to truncate. This truncation leads to an overlap between the compressed header and decompressed data, which can result in the corruption of the routing header in forwarded packets. This vulnerability could allow a remote attacker to cause data corruption.
A flaw was found in the Linux kernel's Virtual Extensible LAN (VXLAN) module. This vulnerability occurs because a cached IP header pointer is improperly reused after a Path Maximum Transmission Unit (PMTU) check. When the packet's head is modified during the PMTU check, the old cached IP header pointer becomes invalid, leading to a Use-After-Free (UAF) condition. This memory corruption flaw can potentially allow an attacker to cause a system crash or execute arbitrary code.
A flaw was found in the Linux kernel's blk-mq component. This use-after-free vulnerability occurs when a task attempts to submit a bio (a data structure for I/O operations) to blk-mq. If the task is interrupted and sleeps after checking for a cached request but before using it, the cached request can be prematurely freed. This can lead to system instability or crashes.
A flaw was found in the Linux kernel's nvmet-auth component. A remote attacker, by sending a specially crafted NVMe-oF (NVMe over Fabrics) authentication reply message, can cause an out-of-bounds read in the kernel's memory. This vulnerability, exploitable pre-authentication, can lead to the disclosure of sensitive information and potentially a denial of service (DoS) on the affected system.
A flaw was found in the dm-verity component of the Linux kernel. A buffer overflow occurs during Forward Error Correction (FEC) calculation, allowing an attacker to write past the end of an allocated buffer. This out-of-bounds write can corrupt the syndrome buffer, potentially leading to system instability or other undefined behavior.
A flaw was found in the Linux kernel's Security-Enhanced Linux (SELinux) module. When using TCP Fast Open, SELinux failed to properly check connect-related permissions. This oversight could allow a local attacker to bypass SELinux network access controls, potentially enabling unauthorized network connections that should have been restricted by security policies.
A flaw was found in the Advanced Linux Sound Architecture (ALSA) usx2y driver in the Linux kernel. A local attacker, by opening the hwdep node of an attached US-X2Y device, could exploit an unbounded memory mapping (mmap) fault offset. This allows read-write access to arbitrary kernel memory, potentially leading to a denial of service (kernel crash) or privilege escalation.
A flaw was found in the Linux kernel's IPv6 networking stack. A use-after-free vulnerability exists in the `ip6_finish_output2()` function, where a cached pointer to the IPv6 destination address can become stale after memory reallocation. An attacker could potentially exploit this to leak sensitive kernel data, misdirect network traffic, or cause a system crash (Denial of Service).
A flaw was found in the Linux kernel's `scsi: qla2xxx` driver. A remote attacker, by sending a specially crafted Fibre Channel Protocol (FCP) response, could cause an integer underflow. This underflow leads to an out-of-bounds read when handling sense data, potentially disclosing sensitive memory information from the kernel's heap.
Loading 1.4 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
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.