RHSA-2026:71602
Vulnerability from csaf_redhat - Published: 2026-09-24 17:10 - Updated: 2026-11-09 23:15A use-after-free vulnerability was identified in the Linux kernel framebuffer console (fbcon) subsystem. During framebuffer unregistration, the kernel freed the memory for a display mode but did not clear the corresponding fb_display[i]->mode pointer. Subsequent framebuffer ioctl operations could then dereference the stale pointer, resulting in a kernel oops or crash.
| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: AppStream-10.2.Z:kernel-64k-debug-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-64k-debug-devel-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-64k-debug-devel-matched-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-64k-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-64k-devel-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-64k-devel-matched-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debug-devel-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debug-devel-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debug-devel-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debug-devel-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debug-devel-matched-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debug-devel-matched-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debug-devel-matched-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debug-devel-matched-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debuginfo-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debuginfo-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debuginfo-common-aarch64-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debuginfo-common-ppc64le-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debuginfo-common-s390x-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debuginfo-common-x86_64-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-devel-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-devel-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-devel-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-devel-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-devel-matched-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-devel-matched-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-devel-matched-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-devel-matched-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-doc-0:6.12.0-211.60.1.el10_2.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-rt-64k-debug-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-rt-64k-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-rt-debug-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-rt-debug-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-rt-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-rt-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-zfcpdump-debuginfo-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-zfcpdump-devel-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-zfcpdump-devel-matched-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:libperf-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:libperf-debuginfo-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:libperf-debuginfo-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:libperf-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:perf-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:perf-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:perf-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:perf-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:perf-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:perf-debuginfo-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:perf-debuginfo-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:perf-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:python3-perf-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:python3-perf-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:python3-perf-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:python3-perf-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:rtla-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:rtla-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:rtla-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:rtla-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:rv-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:rv-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:rv-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:rv-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-0:6.12.0-211.60.1.el10_2.src | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-64k-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-64k-core-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-64k-debug-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-64k-debug-core-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-64k-debug-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-64k-debug-modules-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-64k-debug-modules-core-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-64k-debug-modules-extra-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-64k-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-64k-modules-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-64k-modules-core-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-64k-modules-extra-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-abi-stablelists-0:6.12.0-211.60.1.el10_2.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-core-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-core-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-core-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-core-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-core-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-core-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-core-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-core-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-modules-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-modules-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-modules-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-modules-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-modules-core-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-modules-core-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-modules-core-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-modules-core-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-modules-extra-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-modules-extra-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-modules-extra-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-modules-extra-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-uki-virt-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debuginfo-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debuginfo-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debuginfo-common-aarch64-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debuginfo-common-ppc64le-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debuginfo-common-s390x-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debuginfo-common-x86_64-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-core-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-core-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-core-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-core-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-extra-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-extra-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-extra-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-extra-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-extra-matched-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-extra-matched-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-extra-matched-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-extra-matched-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-rt-64k-debug-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-rt-64k-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-rt-debug-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-rt-debug-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-rt-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-rt-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-tools-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-tools-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-tools-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-tools-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-tools-libs-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-tools-libs-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-tools-libs-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-uki-virt-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-uki-virt-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-uki-virt-addons-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-uki-virt-addons-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-zfcpdump-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-zfcpdump-core-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-zfcpdump-debuginfo-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-zfcpdump-modules-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-zfcpdump-modules-core-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-zfcpdump-modules-extra-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:libperf-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:libperf-debuginfo-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:libperf-debuginfo-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:libperf-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:perf-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:perf-debuginfo-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:perf-debuginfo-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:perf-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-64k-debug-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-64k-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-debuginfo-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-debuginfo-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-debuginfo-common-aarch64-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-debuginfo-common-ppc64le-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-debuginfo-common-s390x-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-debuginfo-common-x86_64-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-rt-64k-debug-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-rt-64k-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-rt-debug-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-rt-debug-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-rt-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-rt-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-tools-libs-devel-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-tools-libs-devel-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-tools-libs-devel-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-zfcpdump-debuginfo-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:libperf-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:libperf-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:libperf-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:libperf-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:libperf-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:libperf-debuginfo-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:libperf-debuginfo-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:libperf-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:perf-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:perf-debuginfo-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:perf-debuginfo-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:perf-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.60.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.60.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-debuginfo-common-x86_64-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-rt-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-rt-core-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-rt-debug-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-rt-debug-core-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-rt-debug-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-rt-debug-devel-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-rt-debug-modules-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-rt-debug-modules-core-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-rt-debug-modules-extra-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-rt-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-rt-devel-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-rt-modules-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-rt-modules-core-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-rt-modules-extra-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:libperf-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:perf-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-64k-debug-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-64k-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-debuginfo-common-aarch64-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-debuginfo-common-x86_64-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-64k-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-64k-core-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-64k-debug-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-64k-debug-core-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-64k-debug-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-64k-debug-devel-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-64k-debug-modules-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-64k-debug-modules-core-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-64k-debug-modules-extra-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-64k-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-64k-devel-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-64k-modules-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-64k-modules-core-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-64k-modules-extra-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-core-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-core-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-debug-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-debug-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-debug-core-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-debug-core-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-debug-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-debug-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-debug-devel-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-debug-devel-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-debug-modules-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-debug-modules-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-debug-modules-core-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-debug-modules-core-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-debug-modules-extra-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-debug-modules-extra-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-devel-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-devel-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-modules-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-modules-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-modules-core-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-modules-core-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-modules-extra-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-modules-extra-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:libperf-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:libperf-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:perf-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:perf-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.60.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.60.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
A use-after-free vulnerability was found in the Ceph client session initialization in the Linux kernel. The have_mon_and_osd_map() function checks map epochs without holding the appropriate locks, racing with concurrent map updates that free the old map. This can result in dereferencing freed memory during CephFS or RBD mount operations.
A flaw was found in the Linux kernel's libceph module. A malicious or compromised Ceph server can provide a corrupted cluster map (osdmap) containing invalid length fields. When the client processes this malformed map, insufficient validation causes an out-of-bounds read, leading to a system crash and Denial of Service (DoS).
A flaw was found in the Linux kernel's libceph module. This flaw allows a Denial of Service (DoS) or potential information disclosure through an out-of-bounds read. When processing authentication completion messages, the system does not verify that the message buffer contains the expected payload length. A malicious network peer can exploit this vulnerability by sending a truncated message, triggering a kernel crash.
A flaw was found in the Linux kernel. This vulnerability allows an attacker to cause a Denial of Service (DoS) by forcing an immediate system crash. In the Ceph storage client component (libceph), malformed or corrupted incremental map data containing an unexpected version number triggers an internal assertion failure instead of being safely rejected. A remote authenticated peer within an established Ceph session can exploit this flaw by sending crafted map updates, leading to a kernel panic that renders the host unavailable.
A flaw was found in the Linux kernel's libceph OSD client. When a connection fault occurs during a sparse read, the sparse-read state is not properly reset. This allows a misbehaving or compromised Ceph OSD server, or a network adversary, to disrupt traffic. As a result, the client can misinterpret new data as a continuation of previous data, leading to a persistent failure mode, repeated errors, and continuous retry loops, effectively causing a Denial of Service (DoS) for Ceph clients performing sparse reads.
A flaw was found in the Linux kernel's `drm/amdgpu/vcn4` component. This vulnerability allows an attacker to trigger an out-of-bounds (OOB) read when parsing decoder messages due to insufficient bounds checking. This could lead to information disclosure, potentially revealing sensitive data from memory.
A flaw was found in the Linux kernel's AMD GPU (Graphics Processing Unit) driver, specifically within the `drm/amdgpu/vcn4` component. This vulnerability allows for an out-of-bounds read when processing an Instruction Buffer (IB). An attacker could potentially exploit this to read sensitive information from memory or cause system instability.
A flaw was found in the Linux kernel's `drm/amdgpu/vcn3` component. This vulnerability, an Out-of-Bounds (OOB) read, occurs when parsing decoder messages without proper boundary checks. A local attacker could potentially exploit this to read sensitive information from memory or cause system instability, leading to a denial of service.
A flaw was found in the Linux kernel. This vulnerability, located in the `drm/amdgpu/userq` component, involves improper handling of memory mappings. A local attacker could potentially exploit a race condition during queue creation, where a memory object is unmapped while another is being assigned to the same address. This could lead to unauthorized access to sensitive memory, potentially resulting in information disclosure or system instability.
A flaw was found in the Linux kernel's af_unix component, specifically within its SOCKMAP feature. This vulnerability stems from the kernel's improper handling of Socket Control Message (SCM) attributes when data is passed to the SOCKMAP layer. This can lead to a use-after-free condition, which may allow an attacker to cause system instability or a denial of service. The issue also contributes to resource leaks of file descriptors and inaccurate reporting of file descriptor counts.
A flaw was found in the Linux kernel's `accel/ivpu` component. This vulnerability, a buffer overflow, occurs when the firmware returns a size larger than the allocated buffer during a metric stream information query. This can lead to an incorrect buffer copy, potentially causing system instability or denial of service.
A flaw was found in the Linux kernel's drm/xe/eustall component. This vulnerability occurs because the `drm_dev_put()` function is called before a stream is disabled and its resources are freed within `xe_eu_stall_stream_close()`. This timing issue can lead to a use-after-free condition, where device structures might be accessed after they have been deallocated. A local attacker could potentially exploit this to cause system instability or a denial of service (DoS).
A flaw was found in the Linux kernel's VirtIO GPU (Graphics Processing Unit) driver. The virtio_gpu_cursor_plane_update() and virtio_gpu_resource_flush() functions fail to properly acquire a required lock, which can lead to a race condition. A local user could exploit this vulnerability by triggering a memory allocation failure on the Direct Rendering Manager (DRM) input/output control (ioctl) cursor path. This improper handling of the lock can result in memory corruption, potentially leading to system instability or other undefined behavior.
A flaw was found in the `drm/amdgpu/vce` component of the Linux kernel. Malicious VCE (Video Codec Engine) command streams with oversized dimensions can cause a 32-bit integer overflow. This overflow bypasses validation, allowing the GPU firmware to perform out-of-bound memory access. This could lead to system instability or potentially arbitrary code execution.
A flaw was found in the Linux kernel's PPPoE (Point-to-Point Protocol over Ethernet) implementation. This vulnerability occurs because a pointer to network packet data is not updated after memory is reallocated, leading to the use of an outdated memory address. An attacker with local access could potentially trigger this condition, causing memory corruption. This could result in a system crash (denial of service) or other unpredictable system behavior.
A flaw was found in the Linux kernel's `drm/amdkfd` component. An integer overflow vulnerability exists in the calculation of a memory allocation size. When processing large input values, this calculation can result in an undersized memory region, which can then be overrun by firmware. This could lead to system instability or a denial of service.
A flaw was found in the `drm/xe` component of the Linux kernel. This vulnerability, a use-after-free, occurs because a `dma-buf` (Direct Memory Access Buffer) reference is not properly held for imported Buffer Objects (BOs). If the exporter of a `dma-buf` is freed while a BO still references its reservation object, a subsequent access can lead to a use-after-free condition. This can result in a system crash, causing a Denial of Service (DoS).
A flaw was found in the `drm/xe/rtp` component of the Linux kernel. This vulnerability arises from the unconditional whitelisting of Output/Availability (OA) registers, which is a security violation. By default, these registers could be whitelisted after system events such as probe, graphics translation (gt) reset, resume, and engine reset. This improper whitelisting could allow a local attacker to gain unauthorized access to privileged OA registers, potentially leading to a security bypass or information disclosure.
A flaw was found in the Linux kernel's amdgpu graphics driver. Improper handling of context pstate overrides can lead to use-after-free and NULL pointer dereferences during context initialization and finalization. A local attacker could exploit this vulnerability to cause system instability or a denial of service (DoS).
A flaw was found in the Linux kernel's IP Virtual Server (IPVS) component. When a synced connection is established, it can incorrectly inherit a "one-packet" flag from its destination. This misconfiguration causes the connection's expiry process to mishandle its cleanup, leaving behind stale memory references. This issue could potentially be exploited by an attacker to cause a denial of service (DoS) or lead to system instability.
A flaw was found in the Linux kernel's NVMe (Non-Volatile Memory Express) over TCP (nvme-tcp) component. A malicious NVMe controller can exploit this vulnerability by sending a Ready to Transfer (R2T) command for a read request. The host system, failing to properly validate the request direction, will then send the contents of its read destination buffer to the controller. This can lead to the disclosure of stale kernel memory data, potentially revealing sensitive information.
Loading 2.2 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.