RHSA-2024:11486
Vulnerability from csaf_redhat - Published: 2024-12-19 00:58 - Updated: 2026-09-14 12:21A flaw was found in the Linux kernel's Bluetooth L2CAP (Logical Link Control and Adaptation Protocol) component. A race condition between channel deletion and timeout handling can lead to a null-pointer dereference in the `l2cap_chan_timeout` function. A local attacker with low privileges could exploit this vulnerability, causing a kernel panic and resulting in a denial of service.
| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:bpftool-debuginfo-0:7.4.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:bpftool-debuginfo-0:7.4.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:bpftool-debuginfo-0:7.4.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:bpftool-debuginfo-0:7.4.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-64k-debug-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-64k-debug-devel-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-64k-debug-devel-matched-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-64k-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-64k-devel-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-64k-devel-matched-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-debug-devel-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-debug-devel-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-debug-devel-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-debug-devel-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-debug-devel-matched-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-debug-devel-matched-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-debug-devel-matched-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-debug-devel-matched-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-debuginfo-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-debuginfo-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-debuginfo-common-aarch64-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-debuginfo-common-ppc64le-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-debuginfo-common-s390x-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-debuginfo-common-x86_64-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-devel-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-devel-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-devel-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-devel-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-devel-matched-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-devel-matched-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-devel-matched-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-devel-matched-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-doc-0:5.14.0-503.19.1.el9_5.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-rt-debug-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-rt-debug-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-rt-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-rt-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-zfcpdump-debuginfo-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-zfcpdump-devel-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:kernel-zfcpdump-devel-matched-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:libperf-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:libperf-debuginfo-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:libperf-debuginfo-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:libperf-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:perf-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:perf-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:perf-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:perf-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:perf-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:perf-debuginfo-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:perf-debuginfo-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:perf-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:rtla-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:rtla-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:rtla-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:rtla-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:rv-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:rv-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:rv-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.5.0.Z.MAIN:rv-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:bpftool-0:7.4.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:bpftool-0:7.4.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:bpftool-0:7.4.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:bpftool-0:7.4.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:bpftool-debuginfo-0:7.4.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:bpftool-debuginfo-0:7.4.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:bpftool-debuginfo-0:7.4.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:bpftool-debuginfo-0:7.4.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-0:5.14.0-503.19.1.el9_5.src | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-64k-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-64k-core-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-64k-debug-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-64k-debug-core-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-64k-debug-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-64k-debug-modules-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-64k-debug-modules-core-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-64k-debug-modules-extra-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-64k-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-64k-modules-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-64k-modules-core-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-64k-modules-extra-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-abi-stablelists-0:5.14.0-503.19.1.el9_5.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-core-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-core-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-core-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-core-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-core-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-core-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-core-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-core-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-modules-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-modules-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-modules-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-modules-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-modules-core-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-modules-core-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-modules-core-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-modules-core-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-modules-extra-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-modules-extra-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-modules-extra-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-modules-extra-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debug-uki-virt-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debuginfo-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debuginfo-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debuginfo-common-aarch64-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debuginfo-common-ppc64le-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debuginfo-common-s390x-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-debuginfo-common-x86_64-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-modules-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-modules-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-modules-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-modules-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-modules-core-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-modules-core-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-modules-core-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-modules-core-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-modules-extra-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-modules-extra-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-modules-extra-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-modules-extra-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-rt-debug-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-rt-debug-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-rt-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-rt-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-tools-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-tools-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-tools-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-tools-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-tools-libs-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-tools-libs-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-tools-libs-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-uki-virt-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-uki-virt-addons-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-zfcpdump-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-zfcpdump-core-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-zfcpdump-debuginfo-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-zfcpdump-modules-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-zfcpdump-modules-core-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:kernel-zfcpdump-modules-extra-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:libperf-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:libperf-debuginfo-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:libperf-debuginfo-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:libperf-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:perf-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:perf-debuginfo-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:perf-debuginfo-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:perf-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:python3-perf-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:python3-perf-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:python3-perf-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:python3-perf-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.5.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:bpftool-debuginfo-0:7.4.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:bpftool-debuginfo-0:7.4.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:bpftool-debuginfo-0:7.4.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:bpftool-debuginfo-0:7.4.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-64k-debug-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-64k-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-debuginfo-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-debuginfo-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-debuginfo-common-aarch64-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-debuginfo-common-ppc64le-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-debuginfo-common-s390x-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-debuginfo-common-x86_64-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-rt-debug-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-rt-debug-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-rt-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-rt-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-tools-libs-devel-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-tools-libs-devel-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-tools-libs-devel-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:kernel-zfcpdump-debuginfo-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:libperf-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:libperf-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:libperf-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:libperf-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:libperf-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:libperf-debuginfo-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:libperf-debuginfo-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:libperf-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:perf-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:perf-debuginfo-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:perf-debuginfo-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:perf-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-503.19.1.el9_5.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-503.19.1.el9_5.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-503.19.1.el9_5.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.5.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.5.0.Z.MAIN:bpftool-debuginfo-0:7.4.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.5.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.5.0.Z.MAIN:kernel-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.5.0.Z.MAIN:kernel-debuginfo-common-x86_64-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.5.0.Z.MAIN:kernel-rt-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.5.0.Z.MAIN:kernel-rt-core-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.5.0.Z.MAIN:kernel-rt-debug-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.5.0.Z.MAIN:kernel-rt-debug-core-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.5.0.Z.MAIN:kernel-rt-debug-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.5.0.Z.MAIN:kernel-rt-debug-devel-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.5.0.Z.MAIN:kernel-rt-debug-kvm-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.5.0.Z.MAIN:kernel-rt-debug-modules-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.5.0.Z.MAIN:kernel-rt-debug-modules-core-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.5.0.Z.MAIN:kernel-rt-debug-modules-extra-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.5.0.Z.MAIN:kernel-rt-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.5.0.Z.MAIN:kernel-rt-devel-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.5.0.Z.MAIN:kernel-rt-kvm-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.5.0.Z.MAIN:kernel-rt-modules-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.5.0.Z.MAIN:kernel-rt-modules-core-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.5.0.Z.MAIN:kernel-rt-modules-extra-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.5.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.5.0.Z.MAIN:libperf-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.5.0.Z.MAIN:perf-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.5.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.5.0.Z.MAIN:bpftool-debuginfo-0:7.4.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.5.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.5.0.Z.MAIN:kernel-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.5.0.Z.MAIN:kernel-debuginfo-common-x86_64-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.5.0.Z.MAIN:kernel-rt-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.5.0.Z.MAIN:kernel-rt-core-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.5.0.Z.MAIN:kernel-rt-debug-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.5.0.Z.MAIN:kernel-rt-debug-core-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.5.0.Z.MAIN:kernel-rt-debug-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.5.0.Z.MAIN:kernel-rt-debug-devel-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.5.0.Z.MAIN:kernel-rt-debug-modules-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.5.0.Z.MAIN:kernel-rt-debug-modules-core-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.5.0.Z.MAIN:kernel-rt-debug-modules-extra-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.5.0.Z.MAIN:kernel-rt-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.5.0.Z.MAIN:kernel-rt-devel-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.5.0.Z.MAIN:kernel-rt-modules-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.5.0.Z.MAIN:kernel-rt-modules-core-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.5.0.Z.MAIN:kernel-rt-modules-extra-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.5.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.5.0.Z.MAIN:libperf-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.5.0.Z.MAIN:perf-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.5.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-503.19.1.el9_5.x86_64 | — |
Vendor Fix
fix
|
In the Linux kernel, the following vulnerability has been resolved: bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE bpf_prog_attach uses attach_type_to_prog_type to enforce proper attach type for BPF_PROG_TYPE_CGROUP_SKB. link_create uses bpf_prog_get and relies on bpf_prog_attach_check_attach_type to properly verify prog_type <> attach_type association. Add missing attach_type enforcement for the link_create case. Otherwise, it's currently possible to attach cgroup_skb prog types to other cgroup hooks.
A flaw was found in the Linux kernel. A local attacker with specific privileges could trigger an invalid memory access within the BPF (Berkeley Packet Filter) verifier's `stacksafe()` function. This out-of-bounds access could lead to a kernel crash, resulting in a Denial of Service (DoS) for the system.
A flaw was found in the Linux kernel's nfsd component. A local attacker with low privileges could exploit a vulnerability where uninitialized stack data is improperly freed. This issue can lead to a system crash, resulting in a denial of service.
A flaw was found in the Linux kernel's extended Berkeley Packet Filter (eBPF) subsystem. A privileged local attacker, with `CAP_SYS_ADMIN` capabilities or root access, could exploit a use-after-free vulnerability in the `bpf_uprobe_multi_link_attach()` function. This issue arises when `bpf_link_prime()` fails, leading to improper memory handling. Successful exploitation could result in memory corruption, potentially allowing for a denial of service or privilege escalation.
A flaw was found in the kernel's Berkeley Packet Filter (BPF) subsystem. A privileged local user can trigger a signed division or modulo overflow when executing a BPF program on an x86_64 system. This overflow can lead to a kernel exception and subsequently cause a system crash, resulting in a Denial of Service (DoS).
In the Linux kernel, the following vulnerability has been resolved: arm64: probes: Remove broken LDR (literal) uprobe support The simulate_ldr_literal() and simulate_ldrsw_literal() functions are unsafe to use for uprobes. Both functions were originally written for use with kprobes, and access memory with plain C accesses. When uprobes was added, these were reused unmodified even though they cannot safely access user memory. There are three key problems: 1) The plain C accesses do not have corresponding extable entries, and thus if they encounter a fault the kernel will treat these as unintentional accesses to user memory, resulting in a BUG() which will kill the kernel thread, and likely lead to further issues (e.g. lockup or panic()). 2) The plain C accesses are subject to HW PAN and SW PAN, and so when either is in use, any attempt to simulate an access to user memory will fault. Thus neither simulate_ldr_literal() nor simulate_ldrsw_literal() can do anything useful when simulating a user instruction on any system with HW PAN or SW PAN. 3) The plain C accesses are privileged, as they run in kernel context, and in practice can access a small range of kernel virtual addresses. The instructions they simulate have a range of +/-1MiB, and since the simulated instructions must itself be a user instructions in the TTBR0 address range, these can address the final 1MiB of the TTBR1 acddress range by wrapping downwards from an address in the first 1MiB of the TTBR0 address range. In contemporary kernels the last 8MiB of TTBR1 address range is reserved, and accesses to this will always fault, meaning this is no worse than (1). Historically, it was theoretically possible for the linear map or vmemmap to spill into the final 8MiB of the TTBR1 address range, but in practice this is extremely unlikely to occur as this would require either: * Having enough physical memory to fill the entire linear map all the way to the final 1MiB of the TTBR1 address range. * Getting unlucky with KASLR randomization of the linear map such that the populated region happens to overlap with the last 1MiB of the TTBR address range. ... and in either case if we were to spill into the final page there would be larger problems as the final page would alias with error pointers. Practically speaking, (1) and (2) are the big issues. Given there have been no reports of problems since the broken code was introduced, it appears that no-one is relying on probing these instructions with uprobes. Avoid these issues by not allowing uprobes on LDR (literal) and LDRSW (literal), limiting the use of simulate_ldr_literal() and simulate_ldrsw_literal() to kprobes. Attempts to place uprobes on LDR (literal) and LDRSW (literal) will be rejected as arm_probe_decode_insn() will return INSN_REJECTED. In future we can consider introducing working uprobes support for these instructions, but this will require more significant work.
A vulnerability was found in the `xfrm` module in the Linux Kernel. This issue was discovered during fuzz testing, where uninitialized memory containing potentially sensitive data was inadvertently copied to user-space. This issue occurs when dumping IPsec algorithm data structures, exposing random padding from the structures. This issue could lead to information leaks if uninitialized memory is accessed by user-space applications.
In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Ignore nCR3[4:0] when loading PDPTEs from memory Ignore nCR3[4:0] when loading PDPTEs from memory for nested SVM, as bits 4:0 of CR3 are ignored when PAE paging is used, and thus VMRUN doesn't enforce 32-byte alignment of nCR3. In the absolute worst case scenario, failure to ignore bits 4:0 can result in an out-of-bounds read, e.g. if the target page is at the end of a memslot, and the VMM isn't using guard pages. Per the APM: The CR3 register points to the base address of the page-directory-pointer table. The page-directory-pointer table is aligned on a 32-byte boundary, with the low 5 address bits 4:0 assumed to be 0. And the SDM's much more explicit: 4:0 Ignored Note, KVM gets this right when loading PDPTRs, it's only the nSVM flow that is broken.
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: Fix UAF on iso_sock_timeout conn->sk maybe have been unlinked/freed while waiting for iso_conn_lock so this checks if the conn->sk is still valid by checking if it part of iso_sk_list.
A use-after-free vulnerability was found in the Linux kernel's Bluetooth SCO. When sco_sock_timeout() is called, conn->sk may be unlinked/freed while waiting for sco_conn_lock. This checks if the conn->sk is still valid by checking if it is part of sco_sk_list, leading to a loss of availability and system confidentiality.
A flaw was found in the Linux kernel's xfrm (IPSec framework) component. A local attacker with low privileges could exploit improper validation of the Security Association (SA) prefix length. This issue arises when the selector family is unspecified, but the SA family is set, leading to a bypass of prefix length limits. Successful exploitation of this vulnerability could result in a denial of service.
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: bnep: fix wild-memory-access in proto_unregister There's issue as follows: KASAN: maybe wild-memory-access in range [0xdead...108-0xdead...10f] CPU: 3 UID: 0 PID: 2805 Comm: rmmod Tainted: G W RIP: 0010:proto_unregister+0xee/0x400 Call Trace: <TASK> __do_sys_delete_module+0x318/0x580 do_syscall_64+0xc1/0x1d0 entry_SYSCALL_64_after_hwframe+0x77/0x7f As bnep_init() ignore bnep_sock_init()'s return value, and bnep_sock_init() will cleanup all resource. Then when remove bnep module will call bnep_sock_cleanup() to cleanup sock's resource. To solve above issue just return bnep_sock_init()'s return value in bnep_exit().
A flaw was found in the Linux kernel. A race condition exists in the irqchip/gic-v4 component, where a local user can force a change of affinity for a Virtual Processing Element (VPE) after it has been unmapped. This occurs because the corresponding doorbell interrupt remains visible, creating a window for exploitation. This vulnerability could lead to a denial of service.
In the Linux kernel, the following vulnerability has been resolved: sched/numa: Fix the potential null pointer dereference in task_numa_work() When running stress-ng-vm-segv test, we found a null pointer dereference error in task_numa_work(). Here is the backtrace: [323676.066985] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000020 ...... [323676.067108] CPU: 35 PID: 2694524 Comm: stress-ng-vm-se ...... [323676.067113] pstate: 23401009 (nzCv daif +PAN -UAO +TCO +DIT +SSBS BTYPE=--) [323676.067115] pc : vma_migratable+0x1c/0xd0 [323676.067122] lr : task_numa_work+0x1ec/0x4e0 [323676.067127] sp : ffff8000ada73d20 [323676.067128] x29: ffff8000ada73d20 x28: 0000000000000000 x27: 000000003e89f010 [323676.067130] x26: 0000000000080000 x25: ffff800081b5c0d8 x24: ffff800081b27000 [323676.067133] x23: 0000000000010000 x22: 0000000104d18cc0 x21: ffff0009f7158000 [323676.067135] x20: 0000000000000000 x19: 0000000000000000 x18: ffff8000ada73db8 [323676.067138] x17: 0001400000000000 x16: ffff800080df40b0 x15: 0000000000000035 [323676.067140] x14: ffff8000ada73cc8 x13: 1fffe0017cc72001 x12: ffff8000ada73cc8 [323676.067142] x11: ffff80008001160c x10: ffff000be639000c x9 : ffff8000800f4ba4 [323676.067145] x8 : ffff000810375000 x7 : ffff8000ada73974 x6 : 0000000000000001 [323676.067147] x5 : 0068000b33e26707 x4 : 0000000000000001 x3 : ffff0009f7158000 [323676.067149] x2 : 0000000000000041 x1 : 0000000000004400 x0 : 0000000000000000 [323676.067152] Call trace: [323676.067153] vma_migratable+0x1c/0xd0 [323676.067155] task_numa_work+0x1ec/0x4e0 [323676.067157] task_work_run+0x78/0xd8 [323676.067161] do_notify_resume+0x1ec/0x290 [323676.067163] el0_svc+0x150/0x160 [323676.067167] el0t_64_sync_handler+0xf8/0x128 [323676.067170] el0t_64_sync+0x17c/0x180 [323676.067173] Code: d2888001 910003fd f9000bf3 aa0003f3 (f9401000) [323676.067177] SMP: stopping secondary CPUs [323676.070184] Starting crashdump kernel... stress-ng-vm-segv in stress-ng is used to stress test the SIGSEGV error handling function of the system, which tries to cause a SIGSEGV error on return from unmapping the whole address space of the child process. Normally this program will not cause kernel crashes. But before the munmap system call returns to user mode, a potential task_numa_work() for numa balancing could be added and executed. In this scenario, since the child process has no vma after munmap, the vma_next() in task_numa_work() will return a null pointer even if the vma iterator restarts from 0. Recheck the vma pointer before dereferencing it in task_numa_work().
A flaw was found in the Linux kernel's Bluetooth Host Controller Interface (HCI) component. A null pointer dereference occurs in the hci_read_supported_codecs function because __hci_cmd_sync_sk() incorrectly returns a NULL value for unknown opcodes. A local attacker with low privileges could exploit this vulnerability to trigger a system crash, resulting in a Denial of Service (DoS).
A flaw was found in the Linux kernel's Berkeley Packet Filter (BPF) component. A privileged local attacker could exploit an out-of-bounds write vulnerability in the `trie_get_next_key()` function. This occurs because the function attempts to write more data than the allocated buffer size, leading to memory corruption. Successful exploitation could result in a denial of service or potentially arbitrary code execution.
Loading 1.7 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.