RHSA-2026:97873
Vulnerability from csaf_redhat - Published: 2026-11-11 01:27 - Updated: 2026-11-11 01:29In the Linux kernel, the following vulnerability has been resolved: netlabel: Fix NULL pointer exception caused by CALIPSO on IPv4 sockets When calling netlbl_conn_setattr(), addr->sa_family is used to determine the function behavior. If sk is an IPv4 socket, but the connect function is called with an IPv6 address, the function calipso_sock_setattr() is triggered. Inside this function, the following code is executed: sk_fullsock(__sk) ? inet_sk(__sk)->pinet6 : NULL; Since sk is an IPv4 socket, pinet6 is NULL, leading to a null pointer dereference. This patch fixes the issue by checking if inet6_sk(sk) returns a NULL pointer before accessing pinet6.
| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-64k-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-64k-debug-devel-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-64k-debug-devel-matched-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-64k-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-64k-devel-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-64k-devel-matched-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-debug-devel-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-debug-devel-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-debug-devel-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-debug-devel-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-debug-devel-matched-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-debug-devel-matched-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-debug-devel-matched-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-debug-devel-matched-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-debuginfo-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-debuginfo-common-aarch64-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-debuginfo-common-ppc64le-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-debuginfo-common-s390x-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-debuginfo-common-x86_64-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-devel-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-devel-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-devel-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-devel-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-devel-matched-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-devel-matched-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-devel-matched-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-devel-matched-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-doc-0:5.14.0-741.20.1.el9_9.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-rt-64k-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-rt-64k-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-rt-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-rt-debug-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-rt-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-rt-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-zfcpdump-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-zfcpdump-devel-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:kernel-zfcpdump-devel-matched-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:libperf-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:libperf-debuginfo-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:libperf-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:libperf-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:perf-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:perf-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:perf-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:perf-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:perf-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:perf-debuginfo-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:perf-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:perf-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:python3-perf-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:python3-perf-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:python3-perf-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:python3-perf-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:rtla-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:rtla-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:rtla-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:rtla-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:rtla-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:rtla-debuginfo-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:rtla-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:rtla-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:rv-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:rv-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:rv-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:rv-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:rv-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:rv-debuginfo-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:rv-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.9.0.Z.MAIN:rv-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-0:5.14.0-741.20.1.el9_9.src | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-64k-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-64k-core-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-64k-debug-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-64k-debug-core-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-64k-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-64k-debug-modules-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-64k-debug-modules-core-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-64k-debug-modules-extra-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-64k-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-64k-modules-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-64k-modules-core-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-64k-modules-extra-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-abi-stablelists-0:5.14.0-741.20.1.el9_9.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-core-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-core-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-core-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-core-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-core-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-core-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-core-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-core-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-modules-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-modules-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-modules-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-modules-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-modules-core-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-modules-core-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-modules-core-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-modules-core-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-modules-extra-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-modules-extra-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-modules-extra-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-modules-extra-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debug-uki-virt-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debuginfo-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debuginfo-common-aarch64-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debuginfo-common-ppc64le-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debuginfo-common-s390x-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-debuginfo-common-x86_64-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-modules-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-modules-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-modules-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-modules-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-modules-core-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-modules-core-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-modules-core-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-modules-core-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-modules-extra-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-modules-extra-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-modules-extra-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-modules-extra-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-rt-64k-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-rt-64k-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-rt-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-rt-debug-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-rt-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-rt-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-tools-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-tools-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-tools-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-tools-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-tools-libs-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-tools-libs-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-tools-libs-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-uki-virt-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-uki-virt-addons-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-zfcpdump-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-zfcpdump-core-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-zfcpdump-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-zfcpdump-modules-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-zfcpdump-modules-core-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:kernel-zfcpdump-modules-extra-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:libperf-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:libperf-debuginfo-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:libperf-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:libperf-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:perf-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:perf-debuginfo-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:perf-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:perf-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:rtla-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:rtla-debuginfo-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:rtla-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:rtla-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:rv-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:rv-debuginfo-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:rv-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.9.0.Z.MAIN:rv-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-64k-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-64k-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-debuginfo-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-debuginfo-common-aarch64-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-debuginfo-common-ppc64le-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-debuginfo-common-s390x-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-debuginfo-common-x86_64-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-rt-64k-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-rt-64k-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-rt-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-rt-debug-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-rt-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-rt-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-tools-libs-devel-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-tools-libs-devel-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-tools-libs-devel-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:kernel-zfcpdump-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:libperf-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:libperf-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:libperf-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:libperf-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:libperf-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:libperf-debuginfo-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:libperf-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:libperf-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:perf-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:perf-debuginfo-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:perf-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:perf-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:rtla-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:rtla-debuginfo-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:rtla-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:rtla-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:rv-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:rv-debuginfo-0:5.14.0-741.20.1.el9_9.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:rv-debuginfo-0:5.14.0-741.20.1.el9_9.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.9.0.Z.MAIN:rv-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-64k-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-64k-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-debuginfo-common-aarch64-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-debuginfo-common-x86_64-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-64k-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-64k-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-core-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-core-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-debug-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-debug-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-debug-core-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-debug-core-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-debug-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-debug-devel-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-debug-devel-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-debug-modules-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-debug-modules-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-debug-modules-core-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-debug-modules-core-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-debug-modules-extra-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-debug-modules-extra-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-devel-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-devel-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-modules-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-modules-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-modules-core-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-modules-core-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-modules-extra-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-rt-modules-extra-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:libperf-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:libperf-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:perf-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:perf-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:rtla-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:rtla-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:rv-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.9.0.Z.MAIN:rv-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-64k-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-64k-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-debug-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-debuginfo-common-aarch64-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-debuginfo-common-x86_64-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-64k-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-64k-core-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-64k-debug-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-64k-debug-core-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-64k-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-64k-debug-devel-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-64k-debug-modules-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-64k-debug-modules-core-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-64k-debug-modules-extra-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-64k-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-64k-devel-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-64k-modules-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-64k-modules-core-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-64k-modules-extra-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-core-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-core-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-debug-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-debug-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-debug-core-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-debug-core-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-debug-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-debug-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-debug-devel-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-debug-devel-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-debug-modules-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-debug-modules-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-debug-modules-core-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-debug-modules-core-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-debug-modules-extra-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-debug-modules-extra-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-devel-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-devel-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-modules-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-modules-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-modules-core-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-modules-core-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-modules-extra-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-rt-modules-extra-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:kernel-tools-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:libperf-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:libperf-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:perf-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:perf-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:python3-perf-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:rtla-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:rtla-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:rv-debuginfo-0:5.14.0-741.20.1.el9_9.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.9.0.Z.MAIN:rv-debuginfo-0:5.14.0-741.20.1.el9_9.x86_64 | — |
Vendor Fix
fix
|
A flaw was found in the Linux kernel's Controller Area Network (CAN) broadcast manager (BCM). Improper locking during runtime updates of internal counters in the bcm_can_tx() function allows a local attacker to trigger a slab-out-of-bounds read access. This vulnerability can lead to information disclosure or a denial of service (DoS) condition, potentially compromising system stability or sensitive data.
In the Linux kernel, the following vulnerability has been resolved: calipso: Don't call calipso functions for AF_INET sk. syzkaller reported a null-ptr-deref in txopt_get(). [0] The offset 0x70 was of struct ipv6_txoptions in struct ipv6_pinfo, so struct ipv6_pinfo was NULL there. However, this never happens for IPv6 sockets as inet_sk(sk)->pinet6 is always set in inet6_create(), meaning the socket was not IPv6 one. The root cause is missing validation in netlbl_conn_setattr(). netlbl_conn_setattr() switches branches based on struct sockaddr.sa_family, which is passed from userspace. However, netlbl_conn_setattr() does not check if the address family matches the socket. The syzkaller must have called connect() for an IPv6 address on an IPv4 socket. We have a proper validation in tcp_v[46]_connect(), but security_socket_connect() is called in the earlier stage. Let's copy the validation to netlbl_conn_setattr(). [0]: Oops: general protection fault, probably for non-canonical address 0xdffffc000000000e: 0000 [#1] PREEMPT SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000070-0x0000000000000077] CPU: 2 UID: 0 PID: 12928 Comm: syz.9.1677 Not tainted 6.12.0 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 RIP: 0010:txopt_get include/net/ipv6.h:390 [inline] RIP: 0010: Code: 02 00 00 49 8b ac 24 f8 02 00 00 e8 84 69 2a fd e8 ff 00 16 fd 48 8d 7d 70 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 53 02 00 00 48 8b 6d 70 48 85 ed 0f 84 ab 01 00 RSP: 0018:ffff88811b8afc48 EFLAGS: 00010212 RAX: dffffc0000000000 RBX: 1ffff11023715f8a RCX: ffffffff841ab00c RDX: 000000000000000e RSI: ffffc90007d9e000 RDI: 0000000000000070 RBP: 0000000000000000 R08: ffffed1023715f9d R09: ffffed1023715f9e R10: ffffed1023715f9d R11: 0000000000000003 R12: ffff888123075f00 R13: ffff88810245bd80 R14: ffff888113646780 R15: ffff888100578a80 FS: 00007f9019bd7640(0000) GS:ffff8882d2d00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f901b927bac CR3: 0000000104788003 CR4: 0000000000770ef0 PKRU: 80000000 Call Trace: <TASK> calipso_sock_setattr+0x56/0x80 net/netlabel/netlabel_calipso.c:557 netlbl_conn_setattr+0x10c/0x280 net/netlabel/netlabel_kapi.c:1177 selinux_netlbl_socket_connect_helper+0xd3/0x1b0 security/selinux/netlabel.c:569 selinux_netlbl_socket_connect_locked security/selinux/netlabel.c:597 [inline] selinux_netlbl_socket_connect+0xb6/0x100 security/selinux/netlabel.c:615 selinux_socket_connect+0x5f/0x80 security/selinux/hooks.c:4931 security_socket_connect+0x50/0xa0 security/security.c:4598 __sys_connect_file+0xa4/0x190 net/socket.c:2067 __sys_connect+0x12c/0x170 net/socket.c:2088 __do_sys_connect net/socket.c:2098 [inline] __se_sys_connect net/socket.c:2095 [inline] __x64_sys_connect+0x73/0xb0 net/socket.c:2095 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xaa/0x1b0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f901b61a12d Code: 02 b8 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f9019bd6fa8 EFLAGS: 00000246 ORIG_RAX: 000000000000002a RAX: ffffffffffffffda RBX: 00007f901b925fa0 RCX: 00007f901b61a12d RDX: 000000000000001c RSI: 0000200000000140 RDI: 0000000000000003 RBP: 00007f901b701505 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f901b5b62a0 R15: 00007f9019bb7000 </TASK> Modules linked in:
A flaw was found in the Linux kernel's thermal core subsystem. When `thermal_zone_device_register_with_trips()` fails during device registration, it does not properly wait for the thermal zone device's removal completion. This can lead to the premature freeing of the device's memory, creating a use-after-free vulnerability. A local attacker could potentially exploit this to cause a denial of service.
A flaw was found in the Linux kernel's `vsock/virtio` component. This vulnerability occurs during zerocopy completion for large messages fragmented into multiple socket kernel buffers (skbs). An issue in how user arguments (uargs) are handled for these buffers can lead to pinned user pages not being properly tracked or released. This prevents the kernel from notifying userspace when these memory pages are safe to reuse, potentially leading to memory leaks or data corruption if pages are prematurely reallocated. This issue could lead to local privilege escalation.
A flaw was found in the Linux kernel's USB serial mxuport driver. A malicious Universal Serial Bus (USB) device could exploit this vulnerability by reporting a bulk-out endpoint maximum packet size smaller than eight bytes. This can lead to user-controlled slab corruption, potentially allowing an attacker to achieve arbitrary code execution.
A flaw was found in the Linux kernel's USB Type-C Port Manager (TCPM) driver. A remote attacker, acting as a malicious USB-C port partner, could exploit an out-of-bounds write vulnerability in the svdm_consume_modes() function. By sending an unsolicited 'Discover Modes ACK' with excessive data, the attacker can cause memory corruption. This could lead to a denial of service or potentially arbitrary code execution on the affected system.
A flaw was found in the Linux kernel's vsock/virtio transport. This vulnerability occurs when the system processes zerocopy socket buffers (skbs) and encounters an error during memory allocation for fixed-buffer vectored data. The system may attempt to free memory incorrectly, leading to a use-after-free condition or memory corruption. This can potentially allow a local attacker to cause a denial of service or escalate their privileges on the system.
A flaw was found in the Linux kernel's mana network driver. In Confidential Virtual Machines (VMs), a missing bounds check when processing network events can allow a malicious hardware component or a compromised VM to write data outside of an intended memory region. This out-of-bounds access could lead to system instability or a denial of service.
A flaw was found in the Linux kernel's mana network driver. This Time-of-Check to Time-of-Use (TOCTOU) vulnerability allows a hardware component to modify a message identifier (hwc_msg_id) in Direct Memory Access (DMA) memory after it has been validated but before it is used. This manipulation bypasses critical bounds validation, potentially leading to unexpected system behavior or security bypasses, particularly in Confidential Virtual Machines (CVMs) where DMA memory is shared and unencrypted.
A flaw was found in the Linux kernel's igc network driver. The `igc_fpe_init_smd_frame()` function, responsible for initializing transmit (TX) buffer fields for Stream-based Data (SMD) frames, does not correctly set the buffer type. This can result in stale XDP (eXpress Data Path) or XSK (AF_XDP socket) types persisting in reused TX buffer entries. Consequently, the system's TX completion process may follow an incorrect cleanup path, potentially leading to memory corruption or system instability.
A flaw was found in the Linux kernel's Intel Ethernet controller driver (idpf). This vulnerability occurs because a critical synchronization mechanism, known as a spinlock, is accessed before it has been properly initialized. An attacker could potentially exploit this timing issue to cause the system to become unstable or crash, leading to a Denial of Service (DoS).
A flaw was found in the Linux kernel's FUSE (Filesystem in Userspace) component. The `fuse_ref_folio()` function does not properly re-lock a request after unlocking it, which can lead to a use-after-free vulnerability. A local attacker could exploit this flaw to potentially execute arbitrary code or cause a denial of service.
A flaw was found in the Linux kernel's Soft iWARP (siw) driver. A remote attacker, by sending specially crafted Read Response segments that exceed the requested length, can trigger an out-of-bounds write. This vulnerability can lead to memory corruption, potentially causing a kernel crash or privilege escalation.
A flaw was found in the Linux kernel. A race condition exists between the `cgroup_writeback_umount()` and `inode_switch_wbs()` functions when a container exits. This race can lead to a kernel panic, resulting in a denial of service. This vulnerability could be triggered by a local user by exiting a container.
A flaw was found in the Linux kernel's ALSA sound driver for the cs35l41 component. This vulnerability occurs because the driver fails to properly remove controls and cancel firmware load work during component unbinding or device removal, especially when firmware autostart is disabled. This can lead to a worker attempting to access driver data that is no longer valid after teardown, resulting in memory corruption. An attacker with local access could potentially exploit this to cause a denial of service or escalate privileges.
A flaw was found in the Linux kernel's ALSA (Advanced Linux Sound Architecture) sequencer component. An unprivileged local user with access to the sound device can exploit a timing window during the cleanup of a queue timer. This allows the user to re-open a timer that has already been closed, leading to a use-after-free vulnerability. This can result in a system crash (denial of service) or potentially lead to arbitrary code execution.
A flaw was found in the Linux kernel's drm/amd/display component. Specifically, within the `dm_update_crtc_state()` function, a stream pointer is released but not subsequently set to NULL. This can lead to a double release of the same pointer if an error occurs later in the process, creating a use-after-free vulnerability. This issue could potentially lead to memory corruption or a denial of service.
A flaw was found in the `drm/amdgpu` component of the Linux kernel. A use-after-unlock vulnerability exists where a virtual machine (VM) pointer is dereferenced after its protective lock has been released. This allows the pointer to be modified, potentially leading to memory corruption. An attacker could exploit this to cause a denial of service or achieve privilege escalation.
A flaw was found in the Linux kernel's DisplayPort (DP) Multi-Stream Transport (MST) subsystem. This vulnerability involves multiple buffer overflows within the `drm_dp_sideband_append_payload()` function when handling data from connected devices. A physically connected, malicious DP MST device can exploit this by sending specially crafted messages, leading to memory corruption. This could potentially allow an attacker to cause system instability or execute unauthorized code.
A flaw was found in the `net/mlx5` driver of the Linux kernel. When the driver attempts to read the MCIA register from a device advertising the `mcia_32dwords` capability, the `mlx5_query_mcia()` function can read more data than the allocated buffer can hold. This leads to a buffer overflow, which can cause a kernel bug and result in a system crash, leading to a Denial of Service (DoS).
A flaw was found in the `vmxnet3` virtual network device driver within the Linux kernel. When processing Geneve-encapsulated packets, the `vmxnet3_get_hdr_len()` function can incorrectly interpret header information, leading to a mismatch between expected and actual packet protocols or IP versions. This can trigger a `BUG_ON` condition, resulting in a kernel panic and a system crash, effectively causing a Denial of Service (DoS).
A flaw was found in the Linux kernel's iSCSI target core. This use-after-free vulnerability occurs in the `core_scsi3_emulate_pro_register_and_move()` function. When processing iSCSI TransportIDs, a memory buffer is prematurely unmapped while still being referenced, particularly when the parameter list spans multiple pages. An attacker could potentially exploit this to cause a system crash, leading to a denial of service.
A flaw was found in the KVM (Kernel-based Virtual Machine) arm64 vgic (Virtual Generic Interrupt Controller) component of the Linux kernel. During interrupt migration, the vgic_prune_ap_list() function temporarily drops and reacquires locks. If an interrupt is removed from the active processor list (ap_list) during this unlocked period, a subsequent check for interrupt affinity may still pass, leading to a double deletion of the interrupt from the list. This double free-like condition could potentially lead to system instability or denial of service.
A flaw was found in the Linux kernel's IP Virtual Server (IPVS) component. This vulnerability occurs when the system processes Internet Control Message Protocol (ICMP) errors originating from network tunnels. Specifically, after stripping outer packet headers, the IPVS component fails to ensure that the inner IP headers are correctly positioned in the packet buffer's headroom. This improper handling of network packet headers could lead to incorrect packet processing, potentially resulting in a denial of service (DoS) or other forms of network instability.
A flaw was found in the Linux kernel's UDP (User Datagram Protocol) tunnel segmentation. This vulnerability arises when the system attempts to process network packets, specifically in the __skb_udp_tunnel_segment() function. An attacker could potentially exploit a use-after-free condition, where the system attempts to use memory that has already been released, leading to system instability or potentially arbitrary code execution.
A flaw was found in the Linux kernel's XFS filesystem. A local attacker, by mounting a specially crafted XFS image, could trigger an out-of-bounds write during log recovery. This vulnerability allows for kernel heap corruption, which could lead to a denial of service or potentially arbitrary code execution.
A flaw was found in the `drm/vmwgfx` component of the Linux kernel. An integer overflow vulnerability exists in the `vmw_shader_define()` function due to improper validation of user-supplied shader window size and offset. When the offset value is close to its maximum, an unsigned addition can wrap around, causing the size check to pass incorrectly. This allows an unbounded offset to be used, which could lead to memory corruption and potentially privilege escalation or denial of service.
A flaw was found in the Linux kernel's Server Message Block over Remote Direct Memory Access (SMC-Rv2) protocol implementation. The `smc_llc_rmt_delete_rkey()` and `smc_llc_save_add_link_rkeys()` functions incorrectly handle oversized LLC messages, reading beyond the intended message boundaries. This can lead to the processing of stale or unintended data from previous messages, potentially resulting in information disclosure or data corruption. A remote attacker could exploit this vulnerability to gain access to sensitive information or cause system instability.
A flaw was found in the Linux kernel's Server Message Block (SMB) client. A remote malicious SMB server could send a specially crafted tree connect response with a byte count that is too small. This incorrect handling can lead to an integer underflow, causing the client to read beyond an allocated memory buffer. Consequently, sensitive information from kernel memory may be exposed to a local user through the `/proc/fs/cifs/DebugData` interface.
A flaw was found in the Linux kernel's vfio/pci component. During device initialization, a memory pointer is not properly cleared after being freed, leading to a use-after-free and double-free vulnerability. A local attacker could exploit this flaw to cause a system crash, resulting in a denial of service, or potentially execute arbitrary code with elevated privileges.
A flaw was found in the Linux kernel's drm/amdkfd component. This vulnerability arises from a race condition where the Micro Engine Scheduler (MES) fails to perform a necessary Translation Lookaside Buffer (TLB) invalidation after unmapping queues. This oversight allows in-flight Direct Memory Access (DMA) descriptors to access memory that has already been unmapped, leading to page faults and potential GPU queue hangs, particularly during Shared Virtual Memory (SVM) page migration.
A flaw was found in the Linux kernel's iSCSI target component. An unauthenticated remote attacker can exploit this vulnerability by sending a specially crafted login payload to an iSCSI portal configured for Challenge-Handshake Authentication Protocol (CHAP). This can lead to an out-of-bounds read, potentially resulting in information disclosure from adjacent memory or a denial of service.
A flaw was found in the Linux kernel's performance events (perf) subsystem. This vulnerability occurs because memory allocated for event address filters is released prematurely while still in active use by other kernel processes. A local user could exploit this use-after-free flaw during performance monitoring operations to cause a Denial of Service (DoS) through a system crash or potentially corrupt system memory.
A flaw was found in the Linux kernel's virtio-fs file system driver. When queue initialization fails—such as when a device advertises more request queues than supported—the driver fails to clear memory pointers after releasing them, resulting in a double-free condition during error cleanup. An attacker capable of presenting a malformed virtio-fs device can exploit this flaw to cause memory corruption, leading to a system crash and Denial of Service (DoS).
A flaw was found in the Linux kernel. When a multi-threaded program sets up a per-thread timer and executes a new program that subsequently fails during startup, the kernel can free timer memory while it remains referenced in an active queue. A local user could exploit this vulnerability to trigger a use-after-free condition, leading to a system crash and Denial of Service (DoS) or potential privilege escalation.
A flaw was found in the Linux kernel's netfilter subsystem. In the flowtable component, connection tracking reference counts are prematurely released before flow entries are fully removed from memory. An attacker could exploit this timing issue during network flow processing, triggering a use-after-free condition. This issue primarily leads to a Denial of Service (DoS) via a system crash or unexpected system instability.
A flaw was found in the Linux kernel's KVM (Kernel-based Virtual Machine) subsystem on ARM64 platforms. During system initialization in protected virtualization modes, the hypervisor fails to revoke host stage-2 access permissions for per-CPU hypervisor stack memory pages. A privileged local host can exploit this flaw to inspect or alter sensitive hypervisor stack data, resulting in a bypass of hypervisor isolation and potential privilege escalation.
A flaw was found in the Linux kernel's NVMe over Fabrics (NVMe-oF) target authentication component. A remote attacker connecting to the NVMe target service can exploit this vulnerability by sending a crafted authentication request, causing a Denial of Service (DoS) through a system crash or potential memory corruption. This issue occurs due to an incorrect buffer size calculation during authentication challenge processing, which allows an undersized buffer to bypass validation checks and results in an out-of-bounds write.
Loading 4.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.