RHSA-2025:2270
Vulnerability from csaf_redhat - Published: 2025-03-05 02:49 - Updated: 2026-09-13 15:32An out-of-bounds (OOB) memory access flaw was found in the i2c driver module in the Linux kernel.
| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: AppStream-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-64k-debug-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-64k-debug-devel-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-64k-debug-devel-matched-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-64k-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-64k-devel-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-64k-devel-matched-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-devel-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-devel-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-devel-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-devel-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-devel-matched-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-devel-matched-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-devel-matched-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-devel-matched-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debuginfo-common-aarch64-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debuginfo-common-ppc64le-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debuginfo-common-s390x-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debuginfo-common-x86_64-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-devel-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-devel-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-devel-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-devel-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-devel-matched-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-devel-matched-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-devel-matched-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-devel-matched-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-doc-0:5.14.0-427.57.1.el9_4.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-rt-debug-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-rt-debug-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-rt-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-rt-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-zfcpdump-debuginfo-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-zfcpdump-devel-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-zfcpdump-devel-matched-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:perf-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:perf-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:perf-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:perf-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:rtla-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:rtla-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:rtla-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:rtla-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:rv-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:rv-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:rv-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:rv-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:bpftool-0:7.3.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:bpftool-0:7.3.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:bpftool-0:7.3.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:bpftool-0:7.3.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-0:5.14.0-427.57.1.el9_4.src | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-64k-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-64k-core-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-64k-debug-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-64k-debug-core-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-64k-debug-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-64k-debug-modules-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-64k-debug-modules-core-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-64k-debug-modules-extra-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-64k-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-64k-modules-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-64k-modules-core-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-64k-modules-extra-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-abi-stablelists-0:5.14.0-427.57.1.el9_4.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-core-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-core-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-core-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-core-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-core-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-core-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-core-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-core-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-modules-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-modules-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-modules-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-modules-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-modules-core-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-modules-core-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-modules-core-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-modules-core-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-modules-extra-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-modules-extra-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-modules-extra-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-modules-extra-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-uki-virt-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debuginfo-common-aarch64-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debuginfo-common-ppc64le-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debuginfo-common-s390x-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debuginfo-common-x86_64-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-core-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-core-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-core-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-core-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-extra-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-extra-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-extra-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-extra-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-rt-debug-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-rt-debug-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-rt-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-rt-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-libs-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-libs-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-libs-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-uki-virt-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-zfcpdump-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-zfcpdump-core-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-zfcpdump-debuginfo-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-zfcpdump-modules-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-zfcpdump-modules-core-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-zfcpdump-modules-extra-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:python3-perf-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:python3-perf-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:python3-perf-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:python3-perf-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-64k-debug-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-64k-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debuginfo-common-aarch64-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debuginfo-common-ppc64le-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debuginfo-common-s390x-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debuginfo-common-x86_64-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-rt-debug-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-rt-debug-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-rt-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-rt-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-tools-libs-devel-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-tools-libs-devel-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-tools-libs-devel-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-zfcpdump-debuginfo-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:libperf-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:libperf-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:libperf-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:libperf-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.57.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.57.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.57.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:kernel-debuginfo-common-x86_64-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:kernel-rt-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:kernel-rt-core-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:kernel-rt-debug-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:kernel-rt-debug-core-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:kernel-rt-debug-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:kernel-rt-debug-devel-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:kernel-rt-debug-kvm-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:kernel-rt-debug-modules-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:kernel-rt-debug-modules-core-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:kernel-rt-debug-modules-extra-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:kernel-rt-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:kernel-rt-devel-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:kernel-rt-kvm-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:kernel-rt-modules-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:kernel-rt-modules-core-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:kernel-rt-modules-extra-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:kernel-debuginfo-common-x86_64-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:kernel-rt-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:kernel-rt-core-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:kernel-rt-debug-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:kernel-rt-debug-core-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:kernel-rt-debug-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:kernel-rt-debug-devel-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:kernel-rt-debug-modules-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:kernel-rt-debug-modules-core-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:kernel-rt-debug-modules-extra-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:kernel-rt-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:kernel-rt-devel-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:kernel-rt-modules-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:kernel-rt-modules-core-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:kernel-rt-modules-extra-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.57.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
In the Linux kernel, the following vulnerability has been resolved: lib/generic-radix-tree.c: Don't overflow in peek() When we started spreading new inode numbers throughout most of the 64 bit inode space, that triggered some corner case bugs, in particular some integer overflows related to the radix tree code. Oops.
In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: Unmap the surface before resetting it on a plane state Switch to a new plane state requires unreferencing of all held surfaces. In the work required for mob cursors the mapped surfaces started being cached but the variable indicating whether the surface is currently mapped was not being reset. This leads to crashes as the duplicated state, incorrectly, indicates the that surface is mapped even when no surface is present. That's because after unreferencing the surface it's perfectly possible for the plane to be backed by a bo instead of a surface. Reset the surface mapped flag when unreferencing the plane state surface to fix null derefs in cleanup. Fixes crashes in KDE KWin 6.0 on Wayland: Oops: 0000 [#1] PREEMPT SMP PTI CPU: 4 PID: 2533 Comm: kwin_wayland Not tainted 6.7.0-rc3-vmwgfx #2 Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020 RIP: 0010:vmw_du_cursor_plane_cleanup_fb+0x124/0x140 [vmwgfx] Code: 00 00 00 75 3a 48 83 c4 10 5b 5d c3 cc cc cc cc 48 8b b3 a8 00 00 00 48 c7 c7 99 90 43 c0 e8 93 c5 db ca 48 8b 83 a8 00 00 00 <48> 8b 78 28 e8 e3 f> RSP: 0018:ffffb6b98216fa80 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff969d84cdcb00 RCX: 0000000000000027 RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff969e75f21600 RBP: ffff969d4143dc50 R08: 0000000000000000 R09: ffffb6b98216f920 R10: 0000000000000003 R11: ffff969e7feb3b10 R12: 0000000000000000 R13: 0000000000000000 R14: 000000000000027b R15: ffff969d49c9fc00 FS: 00007f1e8f1b4180(0000) GS:ffff969e75f00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000028 CR3: 0000000104006004 CR4: 00000000003706f0 Call Trace: <TASK> ? __die+0x23/0x70 ? page_fault_oops+0x171/0x4e0 ? exc_page_fault+0x7f/0x180 ? asm_exc_page_fault+0x26/0x30 ? vmw_du_cursor_plane_cleanup_fb+0x124/0x140 [vmwgfx] drm_atomic_helper_cleanup_planes+0x9b/0xc0 commit_tail+0xd1/0x130 drm_atomic_helper_commit+0x11a/0x140 drm_atomic_commit+0x97/0xd0 ? __pfx___drm_printfn_info+0x10/0x10 drm_atomic_helper_update_plane+0xf5/0x160 drm_mode_cursor_universal+0x10e/0x270 drm_mode_cursor_common+0x102/0x230 ? __pfx_drm_mode_cursor2_ioctl+0x10/0x10 drm_ioctl_kernel+0xb2/0x110 drm_ioctl+0x26d/0x4b0 ? __pfx_drm_mode_cursor2_ioctl+0x10/0x10 ? __pfx_drm_ioctl+0x10/0x10 vmw_generic_ioctl+0xa4/0x110 [vmwgfx] __x64_sys_ioctl+0x94/0xd0 do_syscall_64+0x61/0xe0 ? __x64_sys_ioctl+0xaf/0xd0 ? syscall_exit_to_user_mode+0x2b/0x40 ? do_syscall_64+0x70/0xe0 ? __x64_sys_ioctl+0xaf/0xd0 ? syscall_exit_to_user_mode+0x2b/0x40 ? do_syscall_64+0x70/0xe0 ? exc_page_fault+0x7f/0x180 entry_SYSCALL_64_after_hwframe+0x6e/0x76 RIP: 0033:0x7f1e93f279ed Code: 04 25 28 00 00 00 48 89 45 c8 31 c0 48 8d 45 10 c7 45 b0 10 00 00 00 48 89 45 b8 48 8d 45 d0 48 89 45 c0 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff f> RSP: 002b:00007ffca0faf600 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 000055db876ed2c0 RCX: 00007f1e93f279ed RDX: 00007ffca0faf6c0 RSI: 00000000c02464bb RDI: 0000000000000015 RBP: 00007ffca0faf650 R08: 000055db87184010 R09: 0000000000000007 R10: 000055db886471a0 R11: 0000000000000246 R12: 00007ffca0faf6c0 R13: 00000000c02464bb R14: 0000000000000015 R15: 00007ffca0faf790 </TASK> Modules linked in: snd_seq_dummy snd_hrtimer nf_conntrack_netbios_ns nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_ine> CR2: 0000000000000028 ---[ end trace 0000000000000000 ]--- RIP: 0010:vmw_du_cursor_plane_cleanup_fb+0x124/0x140 [vmwgfx] Code: 00 00 00 75 3a 48 83 c4 10 5b 5d c3 cc cc cc cc 48 8b b3 a8 00 00 00 48 c7 c7 99 90 43 c0 e8 93 c5 db ca 48 8b 83 a8 00 00 00 <48> 8b 78 28 e8 e3 f> RSP: 0018:ffffb6b98216fa80 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff969d84cdcb00 RCX: 0000000000000027 RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff969e75f21600 RBP: ffff969d4143 ---truncated---
In the Linux kernel, the following vulnerability has been resolved: ACPI: LPIT: Avoid u32 multiplication overflow The Linux kernel CVE team has assigned CVE-2023-52683 to this issue. Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024051751-CVE-2023-52683-f280@gregkh/T
In the Linux kernel, the following vulnerability has been resolved: i2c: core: Run atomic i2c xfer when !preemptible Since bae1d3a05a8b, i2c transfers are non-atomic if preemption is disabled. However, non-atomic i2c transfers require preemption (e.g. in wait_for_completion() while waiting for the DMA). panic() calls preempt_disable_notrace() before calling emergency_restart(). Therefore, if an i2c device is used for the restart, the xfer should be atomic. This avoids warnings like: [ 12.667612] WARNING: CPU: 1 PID: 1 at kernel/rcu/tree_plugin.h:318 rcu_note_context_switch+0x33c/0x6b0 [ 12.676926] Voluntary context switch within RCU read-side critical section! ... [ 12.742376] schedule_timeout from wait_for_completion_timeout+0x90/0x114 [ 12.749179] wait_for_completion_timeout from tegra_i2c_wait_completion+0x40/0x70 ... [ 12.994527] atomic_notifier_call_chain from machine_restart+0x34/0x58 [ 13.001050] machine_restart from panic+0x2a8/0x32c Use !preemptible() instead, which is basically the same check as pre-v5.2.
A potential deadlock flaw was found in net/sched/act_mirred.c in the Linux kernel. This may lead to compromised Availability.
In the Linux kernel, the following vulnerability has been resolved: mm/swap: fix race when skipping swapcache The Linux kernel CVE team has assigned CVE-2024-26759 to this issue. Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024040304-CVE-2024-26759-45f1@gregkh/T
A flaw was found in the Linux kernel. Due to an integer overflow, certain EFI-related memory reservations might receive a size other than expected, leading to a denial of service.
In the Linux kernel, the following vulnerability has been resolved: nvme-fc: do not wait in vain when unloading module The module exit path has race between deleting all controllers and freeing 'left over IDs'. To prevent double free a synchronization between nvme_delete_ctrl and ida_destroy has been added by the initial commit. There is some logic around trying to prevent from hanging forever in wait_for_completion, though it does not handling all cases. E.g. blktests is able to reproduce the situation where the module unload hangs forever. If we completely rely on the cleanup code executed from the nvme_delete_ctrl path, all IDs will be freed eventually. This makes calling ida_destroy unnecessary. We only have to ensure that all nvme_delete_ctrl code has been executed before we leave nvme_fc_exit_module. This is done by flushing the nvme_delete_wq workqueue. While at it, remove the unused nvme_fc_wq workqueue too.
In the Linux kernel, the following vulnerability has been resolved: ACPI: processor_idle: Fix memory leak in acpi_processor_power_exit() After unregistering the CPU idle device, the memory associated with it is not freed, leading to a memory leak: unreferenced object 0xffff896282f6c000 (size 1024): comm "swapper/0", pid 1, jiffies 4294893170 hex dump (first 32 bytes): 00 00 00 00 0b 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc 8836a742): [<ffffffff993495ed>] kmalloc_trace+0x29d/0x340 [<ffffffff9972f3b3>] acpi_processor_power_init+0xf3/0x1c0 [<ffffffff9972d263>] __acpi_processor_start+0xd3/0xf0 [<ffffffff9972d2bc>] acpi_processor_start+0x2c/0x50 [<ffffffff99805872>] really_probe+0xe2/0x480 [<ffffffff99805c98>] __driver_probe_device+0x78/0x160 [<ffffffff99805daf>] driver_probe_device+0x1f/0x90 [<ffffffff9980601e>] __driver_attach+0xce/0x1c0 [<ffffffff99803170>] bus_for_each_dev+0x70/0xc0 [<ffffffff99804822>] bus_add_driver+0x112/0x210 [<ffffffff99807245>] driver_register+0x55/0x100 [<ffffffff9aee4acb>] acpi_processor_driver_init+0x3b/0xc0 [<ffffffff990012d1>] do_one_initcall+0x41/0x300 [<ffffffff9ae7c4b0>] kernel_init_freeable+0x320/0x470 [<ffffffff99b231f6>] kernel_init+0x16/0x1b0 [<ffffffff99042e6d>] ret_from_fork+0x2d/0x50 Fix this by freeing the CPU idle device after unregistering it.
In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: Fix Use-After-Free in ovs_ct_exit The Linux kernel CVE team has assigned CVE-2024-27395 to this issue. Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024050836-CVE-2024-27395-573e@gregkh/T
In the Linux kernel, the following vulnerability has been resolved: dyndbg: fix old BUG_ON in >control parser The Linux kernel CVE team has assigned CVE-2024-35947 to this issue. Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024051952-CVE-2024-35947-09bb@gregkh/T
In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix mlx5e_priv_init() cleanup flow The Linux kernel CVE team has assigned CVE-2024-35959 to this issue. Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024052019-CVE-2024-35959-6e06@gregkh/T
In the Linux kernel, the following vulnerability has been resolved: tcp: defer shutdown(SEND_SHUTDOWN) for TCP_SYN_RECV sockets TCP_SYN_RECV state is really special, it is only used by cross-syn connections, mostly used by fuzzers. In the following crash [1], syzbot managed to trigger a divide by zero in tcp_rcv_space_adjust() A socket makes the following state transitions, without ever calling tcp_init_transfer(), meaning tcp_init_buffer_space() is also not called. TCP_CLOSE connect() TCP_SYN_SENT TCP_SYN_RECV shutdown() -> tcp_shutdown(sk, SEND_SHUTDOWN) TCP_FIN_WAIT1 To fix this issue, change tcp_shutdown() to not perform a TCP_SYN_RECV -> TCP_FIN_WAIT1 transition, which makes no sense anyway. When tcp_rcv_state_process() later changes socket state from TCP_SYN_RECV to TCP_ESTABLISH, then look at sk->sk_shutdown to finally enter TCP_FIN_WAIT1 state, and send a FIN packet from a sane socket state. This means tcp_send_fin() can now be called from BH context, and must use GFP_ATOMIC allocations. [1] divide error: 0000 [#1] PREEMPT SMP KASAN NOPTI CPU: 1 PID: 5084 Comm: syz-executor358 Not tainted 6.9.0-rc6-syzkaller-00022-g98369dccd2f8 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 RIP: 0010:tcp_rcv_space_adjust+0x2df/0x890 net/ipv4/tcp_input.c:767 Code: e3 04 4c 01 eb 48 8b 44 24 38 0f b6 04 10 84 c0 49 89 d5 0f 85 a5 03 00 00 41 8b 8e c8 09 00 00 89 e8 29 c8 48 0f af c3 31 d2 <48> f7 f1 48 8d 1c 43 49 8d 96 76 08 00 00 48 89 d0 48 c1 e8 03 48 RSP: 0018:ffffc900031ef3f0 EFLAGS: 00010246 RAX: 0c677a10441f8f42 RBX: 000000004fb95e7e RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: 0000000027d4b11f R08: ffffffff89e535a4 R09: 1ffffffff25e6ab7 R10: dffffc0000000000 R11: ffffffff8135e920 R12: ffff88802a9f8d30 R13: dffffc0000000000 R14: ffff88802a9f8d00 R15: 1ffff1100553f2da FS: 00005555775c0380(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f1155bf2304 CR3: 000000002b9f2000 CR4: 0000000000350ef0 Call Trace: <TASK> tcp_recvmsg_locked+0x106d/0x25a0 net/ipv4/tcp.c:2513 tcp_recvmsg+0x25d/0x920 net/ipv4/tcp.c:2578 inet6_recvmsg+0x16a/0x730 net/ipv6/af_inet6.c:680 sock_recvmsg_nosec net/socket.c:1046 [inline] sock_recvmsg+0x109/0x280 net/socket.c:1068 ____sys_recvmsg+0x1db/0x470 net/socket.c:2803 ___sys_recvmsg net/socket.c:2845 [inline] do_recvmmsg+0x474/0xae0 net/socket.c:2939 __sys_recvmmsg net/socket.c:3018 [inline] __do_sys_recvmmsg net/socket.c:3041 [inline] __se_sys_recvmmsg net/socket.c:3034 [inline] __x64_sys_recvmmsg+0x199/0x250 net/socket.c:3034 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7faeb6363db9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 c1 17 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffcc1997168 EFLAGS: 00000246 ORIG_RAX: 000000000000012b RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007faeb6363db9 RDX: 0000000000000001 RSI: 0000000020000bc0 RDI: 0000000000000005 RBP: 0000000000000000 R08: 0000000000000000 R09: 000000000000001c R10: 0000000000000122 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000001
In the Linux kernel, the following vulnerability has been resolved: ext4: fix mb_cache_entry's e_refcnt leak in ext4_xattr_block_cache_find() Syzbot reports a warning as follows: ============================================ WARNING: CPU: 0 PID: 5075 at fs/mbcache.c:419 mb_cache_destroy+0x224/0x290 Modules linked in: CPU: 0 PID: 5075 Comm: syz-executor199 Not tainted 6.9.0-rc6-gb947cc5bf6d7 RIP: 0010:mb_cache_destroy+0x224/0x290 fs/mbcache.c:419 Call Trace: <TASK> ext4_put_super+0x6d4/0xcd0 fs/ext4/super.c:1375 generic_shutdown_super+0x136/0x2d0 fs/super.c:641 kill_block_super+0x44/0x90 fs/super.c:1675 ext4_kill_sb+0x68/0xa0 fs/ext4/super.c:7327 [...] ============================================ This is because when finding an entry in ext4_xattr_block_cache_find(), if ext4_sb_bread() returns -ENOMEM, the ce's e_refcnt, which has already grown in the __entry_find(), won't be put away, and eventually trigger the above issue in mb_cache_destroy() due to reference count leakage. So call mb_cache_entry_put() on the -ENOMEM error branch as a quick fix.
in linux kernel's kobject_uevent, zap_modalias_env incorrectly calculates the size of the memory block to move, which may cause out of bounds memory access.
A denial of service vulnerability exists in the Linux kernel. A possible divide-by-0 is in the padata_mt_helper() function when the ps->chunk_size is 0. This vulnerability could result in a loss of system availability.
A flaw was found in the Linux kernel's Stream Control Transmission Protocol (SCTP) implementation. A local attacker with low privileges could exploit improper synchronization during concurrent socket operations involving SO_REUSEPORT. This vulnerability, a null-pointer dereference, can lead to a system crash, resulting in a Denial of Service (DoS).
A flaw was found in the Linux kernel's bonding module. A local attacker could exploit a null pointer dereference in the bond_ipsec_offload_ok function. This occurs because the system does not verify the presence of an active slave before attempting to dereference a pointer, which can lead to a system crash and result in a Denial of Service (DoS).
A flaw was found in the Linux kernel's network handling. A local user could craft a specific Generic Segmentation Offload (GSO) packet with UDP Fragmentation Offload (UFO) characteristics. This crafted packet could lead to an underflow in the `qdisc_pkt_len_init()` function, causing a kernel NULL pointer dereference and a system crash, resulting in a Denial of Service (DoS).
In the Linux kernel, the following vulnerability has been resolved: arm64: probes: Remove broken LDR (literal) uprobe support The simulate_ldr_literal() and simulate_ldrsw_literal() functions are unsafe to use for uprobes. Both functions were originally written for use with kprobes, and access memory with plain C accesses. When uprobes was added, these were reused unmodified even though they cannot safely access user memory. There are three key problems: 1) The plain C accesses do not have corresponding extable entries, and thus if they encounter a fault the kernel will treat these as unintentional accesses to user memory, resulting in a BUG() which will kill the kernel thread, and likely lead to further issues (e.g. lockup or panic()). 2) The plain C accesses are subject to HW PAN and SW PAN, and so when either is in use, any attempt to simulate an access to user memory will fault. Thus neither simulate_ldr_literal() nor simulate_ldrsw_literal() can do anything useful when simulating a user instruction on any system with HW PAN or SW PAN. 3) The plain C accesses are privileged, as they run in kernel context, and in practice can access a small range of kernel virtual addresses. The instructions they simulate have a range of +/-1MiB, and since the simulated instructions must itself be a user instructions in the TTBR0 address range, these can address the final 1MiB of the TTBR1 acddress range by wrapping downwards from an address in the first 1MiB of the TTBR0 address range. In contemporary kernels the last 8MiB of TTBR1 address range is reserved, and accesses to this will always fault, meaning this is no worse than (1). Historically, it was theoretically possible for the linear map or vmemmap to spill into the final 8MiB of the TTBR1 address range, but in practice this is extremely unlikely to occur as this would require either: * Having enough physical memory to fill the entire linear map all the way to the final 1MiB of the TTBR1 address range. * Getting unlucky with KASLR randomization of the linear map such that the populated region happens to overlap with the last 1MiB of the TTBR address range. ... and in either case if we were to spill into the final page there would be larger problems as the final page would alias with error pointers. Practically speaking, (1) and (2) are the big issues. Given there have been no reports of problems since the broken code was introduced, it appears that no-one is relying on probing these instructions with uprobes. Avoid these issues by not allowing uprobes on LDR (literal) and LDRSW (literal), limiting the use of simulate_ldr_literal() and simulate_ldrsw_literal() to kprobes. Attempts to place uprobes on LDR (literal) and LDRSW (literal) will be rejected as arm_probe_decode_insn() will return INSN_REJECTED. In future we can consider introducing working uprobes support for these instructions, but this will require more significant work.
Loading 1.8 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.