RHSA-2026:61887
Vulnerability from csaf_opensuse - Published: 2026-09-01 08:34 - Updated: 2026-09-22 04:18A flaw was found in the Linux kernel. This vulnerability occurs when `uretprobes`, a debugging feature that monitors function returns in user-space programs, are used. The kernel's `seccomp` (secure computing mode) mechanism, which restricts system calls a program can make, incorrectly blocks the `uretprobe` system call. This improper filtering can cause applications to crash unexpectedly, leading to a denial of service for affected processes, particularly in containerized environments like Docker.
| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: AppStream-10.2.Z:kernel-64k-debug-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-64k-debug-devel-0:6.12.0-211.50.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.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-64k-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-64k-devel-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-64k-devel-matched-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debug-devel-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debug-devel-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debug-devel-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debug-devel-0:6.12.0-211.50.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.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debug-devel-matched-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debug-devel-matched-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debug-devel-matched-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debuginfo-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debuginfo-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debuginfo-0:6.12.0-211.50.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.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debuginfo-common-ppc64le-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-debuginfo-common-s390x-0:6.12.0-211.50.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.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-devel-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-devel-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-devel-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-devel-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-devel-matched-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-devel-matched-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-devel-matched-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-devel-matched-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-doc-0:6.12.0-211.50.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.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-rt-64k-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-rt-debug-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-rt-debug-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-rt-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-rt-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-zfcpdump-debuginfo-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-zfcpdump-devel-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:kernel-zfcpdump-devel-matched-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:libperf-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:libperf-debuginfo-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:libperf-debuginfo-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:libperf-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:perf-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:perf-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:perf-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:perf-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:perf-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:perf-debuginfo-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:perf-debuginfo-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:perf-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:python3-perf-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:python3-perf-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:python3-perf-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:python3-perf-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:rtla-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:rtla-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:rtla-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:rtla-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:rv-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:rv-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:rv-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: AppStream-10.2.Z:rv-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-0:6.12.0-211.50.1.el10_2.src | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-64k-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-64k-core-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-64k-debug-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-64k-debug-core-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-64k-debug-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-64k-debug-modules-0:6.12.0-211.50.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.50.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.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-64k-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-64k-modules-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-64k-modules-core-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-64k-modules-extra-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-abi-stablelists-0:6.12.0-211.50.1.el10_2.noarch | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-core-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-core-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-core-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-core-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-core-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-core-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-core-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-core-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-modules-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-modules-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-modules-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-modules-0:6.12.0-211.50.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.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-modules-core-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-modules-core-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-modules-core-0:6.12.0-211.50.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.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-modules-extra-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-modules-extra-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debug-modules-extra-0:6.12.0-211.50.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.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debuginfo-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debuginfo-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debuginfo-0:6.12.0-211.50.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.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debuginfo-common-ppc64le-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-debuginfo-common-s390x-0:6.12.0-211.50.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.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-core-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-core-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-core-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-core-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-extra-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-extra-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-extra-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-extra-0:6.12.0-211.50.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.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-extra-matched-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-extra-matched-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-modules-extra-matched-0:6.12.0-211.50.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.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-rt-64k-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-rt-debug-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-rt-debug-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-rt-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-rt-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-tools-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-tools-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-tools-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-tools-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-tools-libs-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-tools-libs-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-tools-libs-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-uki-virt-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-uki-virt-0:6.12.0-211.50.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.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-uki-virt-addons-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-zfcpdump-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-zfcpdump-core-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-zfcpdump-debuginfo-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-zfcpdump-modules-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-zfcpdump-modules-core-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:kernel-zfcpdump-modules-extra-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:libperf-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:libperf-debuginfo-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:libperf-debuginfo-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:libperf-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:perf-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:perf-debuginfo-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:perf-debuginfo-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:perf-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: BaseOS-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.50.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.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-64k-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-debuginfo-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-debuginfo-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-debuginfo-0:6.12.0-211.50.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.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-debuginfo-common-ppc64le-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-debuginfo-common-s390x-0:6.12.0-211.50.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.50.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.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-rt-64k-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-rt-debug-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-rt-debug-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-rt-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-rt-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.50.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.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-tools-libs-devel-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-tools-libs-devel-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:kernel-zfcpdump-debuginfo-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:libperf-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:libperf-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:libperf-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:libperf-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:libperf-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:libperf-debuginfo-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:libperf-debuginfo-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:libperf-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:perf-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:perf-debuginfo-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:perf-debuginfo-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:perf-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.50.1.el10_2.ppc64le | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.50.1.el10_2.s390x | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: CRB-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-debuginfo-0:6.12.0-211.50.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.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-rt-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-rt-core-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-rt-debug-0:6.12.0-211.50.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.50.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.50.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.50.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.50.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.50.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.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-rt-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-rt-devel-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-rt-modules-0:6.12.0-211.50.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.50.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.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:libperf-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:perf-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: NFV-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.50.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.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-64k-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-debug-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-debuginfo-0:6.12.0-211.50.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.50.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.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-64k-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-64k-core-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-64k-debug-0:6.12.0-211.50.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.50.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.50.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.50.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.50.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.50.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.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-64k-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-64k-devel-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-64k-modules-0:6.12.0-211.50.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.50.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.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-core-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-core-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-debug-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-debug-0:6.12.0-211.50.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.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-debug-core-0:6.12.0-211.50.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.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-debug-debuginfo-0:6.12.0-211.50.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.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-debug-devel-0:6.12.0-211.50.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.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-debug-modules-0:6.12.0-211.50.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.50.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.50.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.50.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.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-devel-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-devel-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-modules-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-modules-0:6.12.0-211.50.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.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-modules-core-0:6.12.0-211.50.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.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-rt-modules-extra-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:kernel-tools-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:libperf-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:libperf-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:perf-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:perf-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.50.1.el10_2.aarch64 | — |
Vendor Fix
fix
Workaround
|
|
| Unresolved product id: RT-10.2.Z:python3-perf-debuginfo-0:6.12.0-211.50.1.el10_2.x86_64 | — |
Vendor Fix
fix
Workaround
|
In the Linux kernel, the following vulnerability has been resolved: ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() Blamed commit did not take care of VLAN encapsulations as spotted by syzbot [1]. Use skb_vlan_inet_prepare() instead of pskb_inet_may_pull(). [1] BUG: KMSAN: uninit-value in __INET_ECN_decapsulate include/net/inet_ecn.h:253 [inline] BUG: KMSAN: uninit-value in INET_ECN_decapsulate include/net/inet_ecn.h:275 [inline] BUG: KMSAN: uninit-value in IP6_ECN_decapsulate+0x7a8/0x1fa0 include/net/inet_ecn.h:321 __INET_ECN_decapsulate include/net/inet_ecn.h:253 [inline] INET_ECN_decapsulate include/net/inet_ecn.h:275 [inline] IP6_ECN_decapsulate+0x7a8/0x1fa0 include/net/inet_ecn.h:321 ip6ip6_dscp_ecn_decapsulate+0x16f/0x1b0 net/ipv6/ip6_tunnel.c:729 __ip6_tnl_rcv+0xed9/0x1b50 net/ipv6/ip6_tunnel.c:860 ip6_tnl_rcv+0xc3/0x100 net/ipv6/ip6_tunnel.c:903 gre_rcv+0x1529/0x1b90 net/ipv6/ip6_gre.c:-1 ip6_protocol_deliver_rcu+0x1c89/0x2c60 net/ipv6/ip6_input.c:438 ip6_input_finish+0x1f4/0x4a0 net/ipv6/ip6_input.c:489 NF_HOOK include/linux/netfilter.h:318 [inline] ip6_input+0x9c/0x330 net/ipv6/ip6_input.c:500 ip6_mc_input+0x7ca/0xc10 net/ipv6/ip6_input.c:590 dst_input include/net/dst.h:474 [inline] ip6_rcv_finish+0x958/0x990 net/ipv6/ip6_input.c:79 NF_HOOK include/linux/netfilter.h:318 [inline] ipv6_rcv+0xf1/0x3c0 net/ipv6/ip6_input.c:311 __netif_receive_skb_one_core net/core/dev.c:6139 [inline] __netif_receive_skb+0x1df/0xac0 net/core/dev.c:6252 netif_receive_skb_internal net/core/dev.c:6338 [inline] netif_receive_skb+0x57/0x630 net/core/dev.c:6397 tun_rx_batched+0x1df/0x980 drivers/net/tun.c:1485 tun_get_user+0x5c0e/0x6c60 drivers/net/tun.c:1953 tun_chr_write_iter+0x3e9/0x5c0 drivers/net/tun.c:1999 new_sync_write fs/read_write.c:593 [inline] vfs_write+0xbe2/0x15d0 fs/read_write.c:686 ksys_write fs/read_write.c:738 [inline] __do_sys_write fs/read_write.c:749 [inline] __se_sys_write fs/read_write.c:746 [inline] __x64_sys_write+0x1fb/0x4d0 fs/read_write.c:746 x64_sys_call+0x30ab/0x3e70 arch/x86/include/generated/asm/syscalls_64.h:2 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xd3/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: slab_post_alloc_hook mm/slub.c:4960 [inline] slab_alloc_node mm/slub.c:5263 [inline] kmem_cache_alloc_node_noprof+0x9e7/0x17a0 mm/slub.c:5315 kmalloc_reserve+0x13c/0x4b0 net/core/skbuff.c:586 __alloc_skb+0x805/0x1040 net/core/skbuff.c:690 alloc_skb include/linux/skbuff.h:1383 [inline] alloc_skb_with_frags+0xc5/0xa60 net/core/skbuff.c:6712 sock_alloc_send_pskb+0xacc/0xc60 net/core/sock.c:2995 tun_alloc_skb drivers/net/tun.c:1461 [inline] tun_get_user+0x1142/0x6c60 drivers/net/tun.c:1794 tun_chr_write_iter+0x3e9/0x5c0 drivers/net/tun.c:1999 new_sync_write fs/read_write.c:593 [inline] vfs_write+0xbe2/0x15d0 fs/read_write.c:686 ksys_write fs/read_write.c:738 [inline] __do_sys_write fs/read_write.c:749 [inline] __se_sys_write fs/read_write.c:746 [inline] __x64_sys_write+0x1fb/0x4d0 fs/read_write.c:746 x64_sys_call+0x30ab/0x3e70 arch/x86/include/generated/asm/syscalls_64.h:2 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xd3/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f CPU: 0 UID: 0 PID: 6465 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(none) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
A flaw was found in the Linux kernel's `nfnetlink_cthelper` component. This vulnerability, an out-of-bounds read, occurs in the `nfnl_cthelper_dump_table()` function when a network connection tracking helper is removed during a dump operation, leading to a bypassed bounds check. A local attacker could exploit this to cause a system crash (denial of service) or potentially access sensitive information from kernel memory.
A flaw was found in the Linux kernel's netfilter nf_tables component. This vulnerability allows for duplicate device registration when handling network device registration notifications. Such duplicate registrations can lead to unexpected system behavior or instability.
A flaw was found in the Linux kernel's bonding driver, specifically within the Active-Backup Load Balancing (ALB) receive path. A local attacker can trigger a Use-After-Free (UAF) vulnerability in the rlb_arp_recv function by rapidly bringing a bond interface up and down while receiving Address Resolution Protocol (ARP) messages. This concurrent access to freed memory can lead to a null pointer dereference, resulting in a system crash and a Denial of Service (DoS).
A flaw was found in the Linux kernel's ip6_gre module. An unprivileged user could exploit this vulnerability by migrating a network device, causing the ip6erspan_changelink() function to incorrectly handle network namespace references. This error leads to a use-after-free condition when the original network namespace is destroyed, potentially resulting in a kernel bug and system instability or denial of service.
A flaw was found in the Linux kernel's Network File System Daemon (NFSD). An issue with file access counting in the nfsd4_add_rdaccess_to_wrdeleg function can lead to an extra access count for nfs4_file objects. This prevents the proper freeing of associated resources when the NFS server service is stopped. Consequently, this can trigger a system bug during shutdown, potentially leading to a Denial of Service (DoS) condition.
A flaw was found in the Linux kernel's IOMMU (Input/Output Memory Management Unit) AMD driver. The `clone_alias()` function incorrectly uses the device ID (devid) when handling alias devices. This can lead to the propagation of wrong or stale Device Table Entry (DTE) entries to alias devices, potentially impacting system stability or data integrity.
A flaw was found in the Linux kernel's memory cgroup (memcg) list_lru component. A race condition occurs during the reparenting of list_lru entries when an xarray entry is cleared before its associated lists are fully reparented. This allows concurrent operations to modify list pointers under different locks, leading to memory corruption. This corruption can result in system instability or a denial of service (DoS).
A flaw was found in the Linux kernel, specifically within the zram module. This vulnerability is a use-after-free error, where the system attempts to use a piece of memory after it has been freed. This occurs when the `zram_bvec_write_partial()` function allows an asynchronous read to write into a page that has already been deallocated. Such a flaw can lead to system instability, causing crashes, or in some scenarios, could be exploited by a local attacker to escalate privileges or execute arbitrary code.
A flaw was found in the Linux kernel's memory management, specifically within the huge page mechanism. When a huge page is split, the system updates a counter after releasing a reference to the memory. This timing issue can lead to the system attempting to read from memory that has already been freed, potentially resulting in memory corruption or information disclosure.
A flaw was found in the Linux kernel's `io_ti` USB serial driver. A malicious USB device, when plugged into a host running this driver, can exploit a heap overflow vulnerability in the `get_manuf_info()` function. This occurs because the driver does not properly validate the size of data read from the device's I2C EEPROM against the allocated memory buffer. This improper validation can lead to out-of-bounds memory writes, potentially allowing an attacker to execute arbitrary code or cause a system crash (Denial of Service).
A flaw was found in the Linux kernel's NFSv4/pNFS implementation. The `nfs4_decode_mp_ds_addr` function, responsible for decoding network address information, does not properly handle zero-length `r_addr` opaque data. A malicious or compromised metadata server can exploit this by providing a zero-length `r_addr`, leading to a NULL pointer dereference and causing the client system to panic, resulting in a Denial of Service (DoS).
A flaw was found in the Linux kernel's NFSv4 (Network File System version 4) flexfiles component. This vulnerability occurs when the ff_layout_alloc_lseg() function processes a malformed flexfiles layout that specifies a zero filehandle version count. An attacker could exploit this by providing a specially crafted flexfiles layout, leading to a null-pointer dereference and ultimately causing a kernel panic, resulting in a Denial of Service (DoS) for the system.
A flaw was found in the Linux kernel's Network File System Daemon (nfsd). This vulnerability occurs during the processing of Access Control List (ACL) set operations. If a specific decode step fails, a memory leak of a posix_acl object occurs. This can lead to resource exhaustion over time, potentially resulting in a Denial of Service (DoS) for the affected server.
A flaw was found in the Linux kernel's Network File System Daemon (nfsd). When a `setlease` operation fails, the system prematurely releases a layout state identifier. An attacker could exploit this by triggering the failure, leading to a use-after-free vulnerability. This could result in a system crash, causing a Denial of Service (DoS).
A flaw was found in the Linux kernel's parallel Network File System (pNFS) component. An issue in the `pnfs_update_layout()` function causes a use-after-free vulnerability due to incorrect ordering of memory management operations. This flaw can be triggered when the system attempts to update a pNFS layout, potentially leading to system instability, crashes, or a denial of service. In some scenarios, this type of memory corruption could be exploited by a local attacker to achieve arbitrary code execution.
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 Server Message Block (SMB) client. A missing lock around the `tc_count` increment in the `smb2_find_smb_sess_tcon_unlocked()` function creates a race condition. This vulnerability, caused by an incomplete refactoring of locking mechanisms, could lead to unexpected behavior.
A flaw was found in the Linux kernel's netfilter ipset component. A race condition exists between the `ip_set_list` resize operation and dump operations. This can lead to a use-after-free vulnerability, where memory is accessed after it has been deallocated. A successful exploitation of this flaw could result in a kernel panic, effectively causing a Denial of Service (DoS) on the system.
A flaw was found in the Linux kernel's synaptics-rmi4 input driver. This vulnerability occurs because the driver incorrectly allocates memory for a keymap, leading to an out-of-bounds memory access. A local user with access to a specially crafted input device could exploit this to read or write to unauthorized memory regions. This could result in information disclosure or potentially allow for further system compromise.
A flaw was found in the Linux kernel's `synaptics-rmi4` input driver. The `rmi_f3a_map_gpios()` function incorrectly allocates memory for the `gpio_key_map`, making it smaller than required. This allows a device reporting a specific `gpio_count` value to trigger an out-of-bounds read, leading to information disclosure by leaking adjacent slab memory to user space. Additionally, a local user with access to the `evdev` node can exploit this vulnerability to perform out-of-bounds writes with caller-controlled values, which may lead to further system compromise.
A flaw was found in the Linux kernel's NFSv4 implementation. A local user could exploit a vulnerability where opening a file with O_TRUNC (truncate) and O_RDONLY (read-only) flags would bypass the necessary write permission checks. This oversight allows an attacker to truncate a file without having explicit write access, leading to unauthorized data modification.
A flaw was found in the Linux kernel's QAT (QuickAssist Technology) crypto module. This vulnerability occurs in the RSA key parser when handling CRT (Chinese Remainder Theorem) components. An underflow can happen during a memory copy operation if an RSA CRT component is larger than its allocated buffer, leading to memory corruption. This could potentially allow an attacker to cause system instability or execute arbitrary code.
A flaw was found in the Linux kernel's nvmet subsystem. An unauthenticated remote attacker could exploit an out-of-bounds heap read vulnerability in the Discovery Get Log Page function. By sending a specially crafted request with a manipulated offset, an attacker could read sensitive kernel memory, leading to information disclosure of kernel pointers. This vulnerability could also cause a denial of service by crashing the target host.
A flaw was found in the Linux kernel's Server Message Block (SMB) client. This vulnerability occurs due to a double-free error when handling change notify replies. If a response attempt returns a replayable error and frees its buffer, and then SMB2_notify_init() fails, the same buffer can be freed again. This can lead to memory corruption and potentially a denial of service.
A flaw was found in the Linux kernel's memory management (mm) shrinker subsystem. A race condition exists where the `shrinker_info` array can be prematurely freed while still accessible, leading to a use-after-free or double-free vulnerability. This memory corruption can be exploited by a local attacker to cause system instability or a denial of service.
A flaw was found in the Linux kernel's crypto QAT (QuickAssist Technology) module. A race condition exists during the teardown of Virtual Function to Physical Function (VF2PF) work in the `adf_disable_sriov()` function. This allows a concurrently scheduled or already queued worker to attempt to access memory that has already been freed, leading to a use-after-free vulnerability. This can result in a null-pointer dereference, potentially causing system instability or crashes.
A flaw was found in the Linux kernel's ALSA virtio sound driver. A malicious or buggy virtio device can provide invalid control metadata, such as an unknown control type or an oversized value count. The driver's control handling trusts this unvalidated metadata, leading to out-of-bounds access when processing sound control information. This vulnerability could allow a malicious device to cause a denial of service or potentially other impacts on the system.
A flaw was found in the Linux kernel's memory management (mm/khugepaged) component. A local user could trigger an edge case where unsaved changes to file data (dirty folios) are improperly discarded. This occurs when a file with previous writes is subjected to a specific sequence of memory advice (madvise) operations for transparent huge pages (THPs), leading to data loss.
A flaw was found in the Linux kernel's userfaultfd mechanism. A local attacker with userfaultfd access could register on shadow stack Virtual Memory Areas (VMAs). By discarding a page and injecting a page with chosen return addresses, an attacker could achieve arbitrary code execution. This vulnerability arises from the improper handling of special VMAs, including shadow stacks, allowing for manipulation of memory regions.
An attacker executing code on affected system could inject an interrupt at a precise moment to disrupt "Safe RET", the default Linux mitigation for speculative Return Overflow (SRSO), which could potentially weaken that protection and may result in information disclosure.
A flaw was found in the Linux kernel. The `rt_spin_unlock()` function, and similar real-time (RT) locking mechanisms, incorrectly release Read-Copy-Update (RCU) protection before fully unlocking, leading to a Use-After-Free (UAF) vulnerability. This issue could allow a local attacker to potentially cause a denial of service or achieve privilege escalation.
A flaw was found in the `nvmet-auth` component of the Linux kernel. A remote attacker, by sending a specially crafted `AUTH_RECEIVE` buffer to an NVMe-oF (NVM Express over Fabrics) target with in-band authentication enabled, can trigger a heap out-of-bounds write. This vulnerability arises because the system incorrectly processes the provided buffer length, leading to memory corruption. This can result in a denial of service or other unpredictable system behavior.
Loading 2.9 MB of JSON…
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
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.