RHSA-2026:98047
Vulnerability from csaf_redhat - Published: 2026-11-11 00:54 - Updated: 2026-11-11 02:01A flaw was found in the Linux kernel's netfilter component. This vulnerability occurs because a queued bridge packet can retain a freed bridge master in its skb->dev field until it is reinjected. When the packet is later reinjected, the system attempts to use the freed bridge master, leading to a use-after-free condition. This can result in system instability or a denial of service.
| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: AppStream-9.4.0.Z.E4S:bpftool-debuginfo-0:7.3.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:bpftool-debuginfo-0:7.3.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:bpftool-debuginfo-0:7.3.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:bpftool-debuginfo-0:7.3.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-64k-debug-debuginfo-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-64k-debug-devel-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-64k-debug-devel-matched-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-64k-debuginfo-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-64k-devel-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-64k-devel-matched-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-debug-devel-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-debug-devel-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-debug-devel-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-debug-devel-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-debug-devel-matched-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-debug-devel-matched-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-debug-devel-matched-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-debug-devel-matched-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-debuginfo-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-debuginfo-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-debuginfo-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-debuginfo-common-aarch64-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-debuginfo-common-ppc64le-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-debuginfo-common-s390x-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-debuginfo-common-x86_64-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-devel-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-devel-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-devel-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-devel-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-devel-matched-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-devel-matched-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-devel-matched-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-devel-matched-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-doc-0:5.14.0-427.162.1.el9_4.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-rt-debug-debuginfo-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-rt-debug-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-rt-debuginfo-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-rt-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-zfcpdump-debuginfo-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-zfcpdump-devel-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:kernel-zfcpdump-devel-matched-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:libperf-debuginfo-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:libperf-debuginfo-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:libperf-debuginfo-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:libperf-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:perf-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:perf-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:perf-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:perf-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:perf-debuginfo-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:perf-debuginfo-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:perf-debuginfo-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:perf-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:rtla-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:rtla-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:rtla-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:rtla-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:rv-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:rv-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:rv-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-9.4.0.Z.E4S:rv-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:bpftool-0:7.3.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:bpftool-0:7.3.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:bpftool-0:7.3.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:bpftool-0:7.3.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:bpftool-debuginfo-0:7.3.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:bpftool-debuginfo-0:7.3.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:bpftool-debuginfo-0:7.3.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:bpftool-debuginfo-0:7.3.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-0:5.14.0-427.162.1.el9_4.src | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-64k-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-64k-core-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-64k-debug-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-64k-debug-core-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-64k-debug-debuginfo-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-64k-debug-modules-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-64k-debug-modules-core-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-64k-debug-modules-extra-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-64k-debuginfo-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-64k-modules-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-64k-modules-core-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-64k-modules-extra-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-abi-stablelists-0:5.14.0-427.162.1.el9_4.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-core-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-core-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-core-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-core-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-core-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-core-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-core-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-core-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-modules-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-modules-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-modules-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-modules-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-modules-core-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-modules-core-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-modules-core-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-modules-core-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-modules-extra-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-modules-extra-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-modules-extra-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-modules-extra-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debug-uki-virt-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debuginfo-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debuginfo-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debuginfo-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debuginfo-common-aarch64-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debuginfo-common-ppc64le-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debuginfo-common-s390x-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-debuginfo-common-x86_64-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-modules-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-modules-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-modules-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-modules-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-modules-core-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-modules-core-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-modules-core-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-modules-core-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-modules-extra-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-modules-extra-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-modules-extra-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-modules-extra-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-rt-debug-debuginfo-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-rt-debug-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-rt-debuginfo-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-rt-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-tools-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-tools-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-tools-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-tools-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-tools-libs-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-tools-libs-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-tools-libs-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-uki-virt-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-zfcpdump-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-zfcpdump-core-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-zfcpdump-debuginfo-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-zfcpdump-modules-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-zfcpdump-modules-core-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:kernel-zfcpdump-modules-extra-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:libperf-debuginfo-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:libperf-debuginfo-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:libperf-debuginfo-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:libperf-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:perf-debuginfo-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:perf-debuginfo-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:perf-debuginfo-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:perf-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:python3-perf-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:python3-perf-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:python3-perf-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:python3-perf-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-427.162.1.el9_4.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-427.162.1.el9_4.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-427.162.1.el9_4.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-9.4.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.4.0.Z.E4S:bpftool-debuginfo-0:7.3.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.4.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.4.0.Z.E4S:kernel-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.4.0.Z.E4S:kernel-debuginfo-common-x86_64-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.4.0.Z.E4S:kernel-rt-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.4.0.Z.E4S:kernel-rt-core-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.4.0.Z.E4S:kernel-rt-debug-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.4.0.Z.E4S:kernel-rt-debug-core-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.4.0.Z.E4S:kernel-rt-debug-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.4.0.Z.E4S:kernel-rt-debug-devel-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.4.0.Z.E4S:kernel-rt-debug-kvm-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.4.0.Z.E4S:kernel-rt-debug-modules-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.4.0.Z.E4S:kernel-rt-debug-modules-core-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.4.0.Z.E4S:kernel-rt-debug-modules-extra-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.4.0.Z.E4S:kernel-rt-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.4.0.Z.E4S:kernel-rt-devel-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.4.0.Z.E4S:kernel-rt-kvm-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.4.0.Z.E4S:kernel-rt-modules-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.4.0.Z.E4S:kernel-rt-modules-core-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.4.0.Z.E4S:kernel-rt-modules-extra-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.4.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.4.0.Z.E4S:libperf-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.4.0.Z.E4S:perf-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-9.4.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.4.0.Z.E4S:bpftool-debuginfo-0:7.3.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.4.0.Z.E4S:kernel-debug-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.4.0.Z.E4S:kernel-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.4.0.Z.E4S:kernel-debuginfo-common-x86_64-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.4.0.Z.E4S:kernel-rt-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.4.0.Z.E4S:kernel-rt-core-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.4.0.Z.E4S:kernel-rt-debug-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.4.0.Z.E4S:kernel-rt-debug-core-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.4.0.Z.E4S:kernel-rt-debug-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.4.0.Z.E4S:kernel-rt-debug-devel-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.4.0.Z.E4S:kernel-rt-debug-modules-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.4.0.Z.E4S:kernel-rt-debug-modules-core-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.4.0.Z.E4S:kernel-rt-debug-modules-extra-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.4.0.Z.E4S:kernel-rt-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.4.0.Z.E4S:kernel-rt-devel-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.4.0.Z.E4S:kernel-rt-modules-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.4.0.Z.E4S:kernel-rt-modules-core-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.4.0.Z.E4S:kernel-rt-modules-extra-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.4.0.Z.E4S:kernel-tools-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.4.0.Z.E4S:libperf-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.4.0.Z.E4S:perf-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-9.4.0.Z.E4S:python3-perf-debuginfo-0:5.14.0-427.162.1.el9_4.x86_64 | — |
Vendor Fix
fix
Workaround
|
A flaw was found in the Linux kernel's Bluetooth RFCOMM (Radio Frequency Communication) subsystem. A malicious remote device could exploit this vulnerability by sending specially crafted, truncated Multiplexing Control Channel (MCC) frames. This lack of proper validation of incoming data length before processing could lead to out-of-bounds reads, potentially resulting in information disclosure or a denial of service.
A flaw was found in the Linux kernel's IP Generic Routing Encapsulation (ip_gre) component. This vulnerability allows a local attacker with network administration capabilities in one network namespace to modify a tunnel residing in a different network namespace where they lack privileges. This is due to an insufficient capability check in the `changelink()` function, which only verifies permissions in the device's network namespace and not the tunnel's. Successful exploitation could lead to unauthorized alteration of network tunnel configurations, potentially causing network disruption or redirection of traffic.
A flaw was found in the Linux kernel's Fibre Channel (FC) transport component. An adjacent Fibre Channel fabric actor, such as a compromised switch or fabric controller, can send a specially crafted FPIN ELS (Fabric Performance Incentive Notification Extended Link Service) frame. This malformed frame, specifically with a `pname_count` field that causes an integer overflow, can trigger an infinite loop, leading to a Denial of Service (DoS) in the affected system.
A flaw was found in the Linux kernel's netfilter conntrack TCP state machine. A remote attacker can exploit this vulnerability by sending a specially crafted sequence of TCP (Transmission Control Protocol) packets, specifically a SYN (synchronize) packet followed by an RST (reset) packet with an invalid sequence number. This improper handling of the RST packet can prematurely terminate an active Network Address Translation (NAT) entry, making connection teardown easier than intended and potentially leading to a denial of service for affected connections.
A flaw was found in the Linux kernel's `tunnels` module. This vulnerability occurs when the `iptunnel_pmtud_check_icmp()` function is called without the `skb transport header` being properly set. An attacker could exploit this condition to trigger an out-of-bound memory access, which may lead to system instability or a denial of service.
A flaw was found in the Linux kernel's tunnels module. This vulnerability, categorized as a Use-After-Free (UAF), arises from improper handling of network header pointers during certain packet processing operations. Specifically, functions responsible for building Internet Control Message Protocol (ICMP) packets for Path MTU Discovery (PMTUD) cache header information before memory reallocations, which can lead to the use of freed memory. A local attacker could potentially leverage this to cause a system crash, resulting in a denial of service.
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 NVMe over TCP target (nvmet-tcp) implementation. When a data digest mismatch is detected, nvmet_req_uninit() is called unconditionally, but if the command was already in the INIT_FAILED state, the matching percpu_ref_tryget_live() was never performed. The resulting percpu_ref_put() underflows the reference counter, which can lead to premature freeing of the referenced object (use-after-free) and a permanent workqueue deadlock. A remote attacker with access to the NVMe/TCP target can exploit this by sending a packet with an invalid data digest to crash the target (Denial of Service), with potential for memory corruption through the refcount underflow.
A flaw was found in the libceph component of the Linux kernel. A remote attacker could send a specially crafted monitor map (monmap) that advertises zero monitors. This malformed monmap is incorrectly processed as valid, which can lead to a client crash when attempting to open a session. This vulnerability results in a Denial of Service (DoS) for the client.
A flaw was found in the `libceph` component of the Linux kernel. During an authorizer update, if the authorizer is rebuilt, a stale pointer to a freed memory region can be retained. A remote attacker could exploit this by triggering a specific network reconnection, leading to a use-after-free vulnerability. This memory corruption could result in a system crash or denial of service.
A flaw was found in libceph, a component of the Linux kernel. When processing a malformed CRUSH map, if a parent bucket's name exists but its type is missing, a null pointer dereference can occur. This issue can lead to a system crash, resulting in a Denial of Service (DoS).
A flaw was found in libceph in the Linux kernel. A remote attacker, acting as a malicious monitor, could send a specially crafted OSDMap (Object Storage Device Map) with an overly long pg_temp or pg_upmap entry. This could lead to a stack out-of-bounds write, resulting in a kernel bug and potentially a denial of service.
A flaw was found in the Linux kernel's VXLAN (Virtual Extensible LAN) implementation. A local attacker, with `CAP_NET_ADMIN` (network administration capability) in one network namespace, could exploit an incorrect privilege check in the `rtnl changelink` path. This allows the attacker to modify the configuration of a VXLAN device whose underlying network interface resides in a different network namespace where the attacker lacks the necessary privileges, potentially leading to unauthorized network configuration changes.
A flaw was found in the Linux kernel's IP Virtual Server (IPVS) module. When processing network packets, a buffer reallocation can leave an IP header pointer referencing freed memory. An attacker could exploit this use-after-free condition to cause a Denial of Service (DoS) by crashing the system or potentially corrupt system memory.
A flaw was found in the Linux kernel's `ip6_gre` and `ip6erspan` tunnel drivers. The `changelink` functions in these drivers do not adequately verify administrative capabilities (`CAP_NET_ADMIN`) across different network namespaces. This allows a local attacker, who has `CAP_NET_ADMIN` in one network namespace but not in the tunnel's network namespace, to modify the tunnel's configuration. This could lead to unauthorized changes to network tunnel settings.
A flaw was found in the Linux kernel's netfilter component, specifically within the `nf_queue` functionality. When a bridged packet is queued to NFQUEUE, it can retain a reference to a bridge's private fake destination ('dst') even after the bridge teardown has begun. This can lead to a use-after-free vulnerability, where memory is accessed after it has been deallocated, potentially causing system instability or a denial of service.
A flaw was found in the Linux kernel's netfilter Session Initiation Protocol (SIP) connection tracking module (nf_conntrack_sip). A remote attacker could send specially crafted SIP messages that cause an integer overflow during Network Address Translation (NAT) rewrite delta calculations. This overflow leads to a use-after-free vulnerability, which can result in memory corruption and potentially a denial of service or arbitrary code execution.
A flaw was found in the Linux kernel's IP Virtual Server (IPVS) component. When processing Internet Control Message Protocol (ICMP) errors for tunneled packets, the system can incorrectly use a stale IPv4 option offset. A remote attacker could exploit this by sending a specially crafted ICMP packet, leading to a stack out-of-bounds write. This vulnerability could result in a denial of service or potentially arbitrary code execution.
A flaw was found in the Linux kernel's IP Virtual Server (IPVS) component. When a synced connection is established, it can incorrectly inherit a "one-packet" flag from its destination. This misconfiguration causes the connection's expiry process to mishandle its cleanup, leaving behind stale memory references. This issue could potentially be exploited by an attacker to cause a denial of service (DoS) or lead to system instability.
A flaw was found in the Linux kernel's NVMe (Non-Volatile Memory Express) over TCP (nvme-tcp) component. A malicious NVMe controller can exploit this vulnerability by sending a Ready to Transfer (R2T) command for a read request. The host system, failing to properly validate the request direction, will then send the contents of its read destination buffer to the controller. This can lead to the disclosure of stale kernel memory data, potentially revealing sensitive information.
A flaw was found in the Linux kernel's netfilter connection tracking subsystem. The TCP option processing mechanism improperly assumes memory alignment when reading packet headers. A remote attacker could exploit this vulnerability by sending crafted TCP packets with misaligned SACK options through a system running conntrack (e.g., Linux firewall/NAT using iptables/nftables), causing a memory access fault that leads to a kernel panic and Denial of Service (DoS).
Loading 1.8 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.