RHSA-2025:13135
Vulnerability from csaf_redhat - Published: 2025-08-06 08:01 - Updated: 2026-08-18 20:57In the Linux kernel, the following vulnerability has been resolved: serial: core: fix transmit-buffer reset and memleak Commit 761ed4a94582 ("tty: serial_core: convert uart_close to use tty_port_close") converted serial core to use tty_port_close() but failed to notice that the transmit buffer still needs to be freed on final close. Not freeing the transmit buffer means that the buffer is no longer cleared on next open so that any ioctl() waiting for the buffer to drain might wait indefinitely (e.g. on termios changes) or that stale data can end up being transmitted in case tx is restarted. Furthermore, the buffer of any port that has been opened would leak on driver unbind. Note that the port lock is held when clearing the buffer pointer due to the ldisc race worked around by commit a5ba1d95e46e ("uart: fix race between uart_put_char() and uart_shutdown()"). Also note that the tty-port shutdown() callback is not called for console ports so it is not strictly necessary to free the buffer page after releasing the lock (cf. d72402145ace ("tty/serial: do not free trasnmit buffer page under port lock")).
| Product | Identifier | Version | Remediation |
|---|---|---|---|
| Unresolved product id: AppStream-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.81.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.81.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.81.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.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-64k-debuginfo-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-64k-devel-0:5.14.0-427.81.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.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.81.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.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-devel-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-devel-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-devel-0:5.14.0-427.81.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.81.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.81.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.81.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.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.81.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.81.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.81.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.81.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.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-devel-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-devel-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-devel-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-devel-0:5.14.0-427.81.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.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-devel-matched-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-devel-matched-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-devel-matched-0:5.14.0-427.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-doc-0:5.14.0-427.81.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.81.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.81.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.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-rt-debuginfo-0:5.14.0-427.81.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.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.81.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.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-zfcpdump-devel-0:5.14.0-427.81.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.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:perf-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:perf-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:perf-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:perf-0:5.14.0-427.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.81.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.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:rtla-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:rtla-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:rtla-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:rtla-0:5.14.0-427.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:rv-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:rv-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:rv-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: AppStream-9.4.0.Z.EUS:rv-0:5.14.0-427.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:bpftool-0:7.3.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:bpftool-0:7.3.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:bpftool-0:7.3.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:bpftool-0:7.3.0-427.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-0:5.14.0-427.81.1.el9_4.src | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-0:5.14.0-427.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-64k-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-64k-core-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-64k-debug-0:5.14.0-427.81.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.81.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.81.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.81.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.81.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.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-64k-debuginfo-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-64k-modules-0:5.14.0-427.81.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.81.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.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-abi-stablelists-0:5.14.0-427.81.1.el9_4.noarch | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-core-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-core-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-core-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-core-0:5.14.0-427.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-0:5.14.0-427.81.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.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-core-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-core-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-core-0:5.14.0-427.81.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.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.81.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.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-modules-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-modules-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-modules-0:5.14.0-427.81.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.81.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.81.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.81.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.81.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.81.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.81.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.81.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.81.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.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.81.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.81.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.81.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.81.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.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-0:5.14.0-427.81.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.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-core-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-core-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-core-0:5.14.0-427.81.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.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-extra-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-extra-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-extra-0:5.14.0-427.81.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.81.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.81.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.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-rt-debuginfo-0:5.14.0-427.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-0:5.14.0-427.81.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.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.81.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.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-libs-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-libs-0:5.14.0-427.81.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.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-zfcpdump-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-zfcpdump-core-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-zfcpdump-debuginfo-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-zfcpdump-modules-0:5.14.0-427.81.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.81.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.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:python3-perf-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:python3-perf-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:python3-perf-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:python3-perf-0:5.14.0-427.81.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.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: BaseOS-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.81.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.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-64k-debuginfo-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.81.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.81.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.81.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.81.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.81.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.81.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.81.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.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-rt-debuginfo-0:5.14.0-427.81.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.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.81.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.81.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.81.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.81.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.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:libperf-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:libperf-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:libperf-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:libperf-0:5.14.0-427.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.81.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.81.1.el9_4.aarch64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.81.1.el9_4.ppc64le | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.81.1.el9_4.s390x | — |
Vendor Fix
fix
|
|
| Unresolved product id: CRB-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.81.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.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.81.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.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:kernel-rt-0:5.14.0-427.81.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.81.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.81.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.81.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.81.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.81.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.81.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.81.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.81.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.81.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.81.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.81.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.81.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.81.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.81.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.81.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.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: NFV-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.81.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.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.81.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.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.81.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.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:kernel-rt-0:5.14.0-427.81.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.81.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.81.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.81.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.81.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.81.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.81.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.81.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.81.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.81.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.81.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.81.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.81.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.81.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.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
|
| Unresolved product id: RT-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.81.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.81.1.el9_4.x86_64 | — |
Vendor Fix
fix
|
A flaw was found in the Linux kernel. A potential memleak in papr_get_attr() may lead to compromised availability.
A vulnerability was found in the Linux kernel's user mode (um) subsystem, specifically within the Local Descriptor Table (LDT) setup functionality. The issue arises from the syscall_stub_data() function misinterpreting the data_count parameter as a byte count rather than a count of longs, leading to an out-of-bounds read. This flaw could expose sensitive kernel memory and cause system instability.
In the Linux kernel, the following vulnerability has been resolved: misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram() `struct vmci_event_qp` allocated by qp_notify_peer() contains padding, which may carry uninitialized data to the userspace, as observed by KMSAN: BUG: KMSAN: kernel-infoleak in instrument_copy_to_user ./include/linux/instrumented.h:121 instrument_copy_to_user ./include/linux/instrumented.h:121 _copy_to_user+0x5f/0xb0 lib/usercopy.c:33 copy_to_user ./include/linux/uaccess.h:169 vmci_host_do_receive_datagram drivers/misc/vmw_vmci/vmci_host.c:431 vmci_host_unlocked_ioctl+0x33d/0x43d0 drivers/misc/vmw_vmci/vmci_host.c:925 vfs_ioctl fs/ioctl.c:51 ... Uninit was stored to memory at: kmemdup+0x74/0xb0 mm/util.c:131 dg_dispatch_as_host drivers/misc/vmw_vmci/vmci_datagram.c:271 vmci_datagram_dispatch+0x4f8/0xfc0 drivers/misc/vmw_vmci/vmci_datagram.c:339 qp_notify_peer+0x19a/0x290 drivers/misc/vmw_vmci/vmci_queue_pair.c:1479 qp_broker_attach drivers/misc/vmw_vmci/vmci_queue_pair.c:1662 qp_broker_alloc+0x2977/0x2f30 drivers/misc/vmw_vmci/vmci_queue_pair.c:1750 vmci_qp_broker_alloc+0x96/0xd0 drivers/misc/vmw_vmci/vmci_queue_pair.c:1940 vmci_host_do_alloc_queuepair drivers/misc/vmw_vmci/vmci_host.c:488 vmci_host_unlocked_ioctl+0x24fd/0x43d0 drivers/misc/vmw_vmci/vmci_host.c:927 ... Local variable ev created at: qp_notify_peer+0x54/0x290 drivers/misc/vmw_vmci/vmci_queue_pair.c:1456 qp_broker_attach drivers/misc/vmw_vmci/vmci_queue_pair.c:1662 qp_broker_alloc+0x2977/0x2f30 drivers/misc/vmw_vmci/vmci_queue_pair.c:1750 Bytes 28-31 of 48 are uninitialized Memory access of size 48 starts at ffff888035155e00 Data copied to user address 0000000020000100 Use memset() to prevent the infoleaks. Also speculatively fix qp_notify_peer_local(), which may suffer from the same problem.
A flaw was found in the Linux kernel, specifically affecting the PowerPC architecture's pseries memory hotplug functionality. The issue arises from the dlpar_memory_remove_by_index() function, which may access memory beyond the bounds of the drmem logical memory block (LMB) array when it fails to find a matching entry for a given Dynamic Reconfiguration Connector (DRC) index. This out-of-bounds access can lead to unintended behavior, including potential system crashes or exposure of sensitive information.
In the Linux kernel, the following vulnerability has been resolved: media: gspca: cpia1: shift-out-of-bounds in set_flicker Syzkaller reported the following issue: UBSAN: shift-out-of-bounds in drivers/media/usb/gspca/cpia1.c:1031:27 shift exponent 245 is too large for 32-bit type 'int' When the value of the variable "sd->params.exposure.gain" exceeds the number of bits in an integer, a shift-out-of-bounds error is reported. It is triggered because the variable "currentexp" cannot be left-shifted by more than the number of bits in an integer. In order to avoid invalid range during left-shift, the conditional expression is added.
In the Linux kernel, the following vulnerability has been resolved: usb: typec: tcpm: Fix NULL pointer dereference in tcpm_pd_svdm() It is possible that typec_register_partner() returns ERR_PTR on failure. When port->partner is an error, a NULL pointer dereference may occur as shown below. [91222.095236][ T319] typec port0: failed to register partner (-17) ... [91225.061491][ T319] Unable to handle kernel NULL pointer dereference at virtual address 000000000000039f [91225.274642][ T319] pc : tcpm_pd_data_request+0x310/0x13fc [91225.274646][ T319] lr : tcpm_pd_data_request+0x298/0x13fc [91225.308067][ T319] Call trace: [91225.308070][ T319] tcpm_pd_data_request+0x310/0x13fc [91225.308073][ T319] tcpm_pd_rx_handler+0x100/0x9e8 [91225.355900][ T319] kthread_worker_fn+0x178/0x58c [91225.355902][ T319] kthread+0x150/0x200 [91225.355905][ T319] ret_from_fork+0x10/0x30 Add a check for port->partner to avoid dereferencing a NULL pointer.
A flaw was found in the Linux kernel related to the Extensible Host Controller Interface (xHCI) subsystem, specifically how it handles certain events. The issue arises when the xHCI driver improperly handles isochronous (isoc) Babble and Buffer Overrun events. The vulnerability occurs because the xHCI driver incorrectly assumes that the xHC (host controller) has released its ownership of a multi-TRB (Transfer Request Block) TD (Transfer Descriptor) after reporting an error on an early TRB. This assumption leads to the premature release of the TD, allowing remaining TRBs to be freed or overwritten, which can cause system instability or crashes.
In the Linux kernel, the following vulnerability has been resolved: USB: core: Fix deadlock in usb_deauthorize_interface() The Linux kernel CVE team has assigned CVE-2024-26934 to this issue. Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024050123-CVE-2024-26934-e2fc@gregkh/T
In the Linux kernel, the following vulnerability has been resolved: usb: xhci: Add error handling in xhci_map_urb_for_dma The Linux kernel CVE team has assigned CVE-2024-26964 to this issue. Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024050130-CVE-2024-26964-54c8@gregkh/T
In the Linux kernel, the following vulnerability has been resolved: USB: usb-storage: Prevent divide-by-0 error in isd200_ata_command The isd200 sub-driver in usb-storage uses the HEADS and SECTORS values in the ATA ID information to calculate cylinder and head values when creating a CDB for READ or WRITE commands. The calculation involves division and modulus operations, which will cause a crash if either of these values is 0. While this never happens with a genuine device, it could happen with a flawed or subversive emulation, as reported by the syzbot fuzzer. Protect against this possibility by refusing to bind to the device if either the ATA_ID_HEADS or ATA_ID_SECTORS value in the device's ID information is 0. This requires isd200_Initialization() to return a negative error code when initialization fails; currently it always returns 0 (even when there is an error).
In the Linux kernel, the following vulnerability has been resolved: net/smc: fix neighbour and rtable leak in smc_ib_find_route() In smc_ib_find_route(), the neighbour found by neigh_lookup() and rtable resolved by ip_route_output_flow() are not released or put before return. It may cause the refcount leak, so fix it.
CWE-401 - Missing Release of Memory after Effective LifetimeA possible use-after-free was found in the Linux kernel in mm/list_lru.c.
In the Linux kernel, the following vulnerability has been resolved: media: uvcvideo: Fix double free in error path If the uvc_status_init() function fails to allocate the int_urb, it will free the dev->status pointer but doesn't reset the pointer to NULL. This results in the kfree() call in uvc_status_cleanup() trying to double-free the memory. Fix it by resetting the dev->status pointer to NULL after freeing it. Reviewed by: Ricardo Ribalda <ribalda@chromium.org>
A dangling pointer vulnerability was found in the Linux kernel. When an async control is written, a copy of a pointer is made in the file handle that started the operation. If the user closes that file descriptor, its structure will be freed and there will be one dangling pointer per pending async control that the driver will try to use, leading to denial of service of the system.
A use-after-free vulnerability was found in the Linux kernel's padata subsystem, in the `padata_reorder()` function. Caused by improper synchronization controls, this vulnerability can occur when a reference-counted data structure (`pd`) is decremented in one thread, freeing it, while another thread still holds a pointer to it and attempts to access it via `padata_find_next()`. This vulnerability can lead to system instability, denial of service, and potential privilege escalation.
In the Linux kernel, the following vulnerability has been resolved: HID: intel-ish-hid: Fix use-after-free issue in ishtp_hid_remove() The system can experience a random crash a few minutes after the driver is removed. This issue occurs due to improper handling of memory freeing in the ishtp_hid_remove() function. The function currently frees the `driver_data` directly within the loop that destroys the HID devices, which can lead to accessing freed memory. Specifically, `hid_destroy_device()` uses `driver_data` when it calls `hid_ishtp_set_feature()` to power off the sensor, so freeing `driver_data` beforehand can result in accessing invalid memory. This patch resolves the issue by storing the `driver_data` in a temporary variable before calling `hid_destroy_device()`, and then freeing the `driver_data` after the device is destroyed.
In the Linux kernel, the following vulnerability has been resolved: x86/microcode/AMD: Fix out-of-bounds on systems with CPU-less NUMA nodes Currently, load_microcode_amd() iterates over all NUMA nodes, retrieves their CPU masks and unconditionally accesses per-CPU data for the first CPU of each mask. According to Documentation/admin-guide/mm/numaperf.rst: "Some memory may share the same node as a CPU, and others are provided as memory only nodes." Therefore, some node CPU masks may be empty and wouldn't have a "first CPU". On a machine with far memory (and therefore CPU-less NUMA nodes): - cpumask_of_node(nid) is 0 - cpumask_first(0) is CONFIG_NR_CPUS - cpu_data(CONFIG_NR_CPUS) accesses the cpu_info per-CPU array at an index that is 1 out of bounds This does not have any security implications since flashing microcode is a privileged operation but I believe this has reliability implications by potentially corrupting memory while flashing a microcode update. When booting with CONFIG_UBSAN_BOUNDS=y on an AMD machine that flashes a microcode update. I get the following splat: UBSAN: array-index-out-of-bounds in arch/x86/kernel/cpu/microcode/amd.c:X:Y index 512 is out of range for type 'unsigned long[512]' [...] Call Trace: dump_stack __ubsan_handle_out_of_bounds load_microcode_amd request_microcode_amd reload_store kernfs_fop_write_iter vfs_write ksys_write do_syscall_64 entry_SYSCALL_64_after_hwframe Change the loop to go over only NUMA nodes which have CPUs before determining whether the first CPU on the respective node needs microcode update. [ bp: Massage commit message, fix typo. ]
A use-after-free vulnerability has been identified in the Linux kernel's HFSC (Hierarchical Fair Service Curve) queuing discipline when it is configured with NETEM (Network Emulation) as a child. This flaw can lead to a kernel panic or crash due to incorrect assumptions about the queue state. Exploitation of this vulnerability requires local access with CAP_NET_ADMIN privileges and control over the qdisc (queueing discipline) setup. A local attacker could leverage this flaw to achieve denial of service or escalate privileges. Given that it affects kernel memory structures, successful exploitation could result in memory corruption, data leaks, or arbitrary write capabilities, leading to a full kernel crash.
In the Linux kernel, the following vulnerability has been resolved: mm/huge_memory: fix dereferencing invalid pmd migration entry When migrating a THP, concurrent access to the PMD migration entry during a deferred split scan can lead to an invalid address access, as illustrated below. To prevent this invalid access, it is necessary to check the PMD migration entry and return early. In this context, there is no need to use pmd_to_swp_entry and pfn_swap_entry_to_page to verify the equality of the target folio. Since the PMD migration entry is locked, it cannot be served as the target. Mailing list discussion and explanation from Hugh Dickins: "An anon_vma lookup points to a location which may contain the folio of interest, but might instead contain another folio: and weeding out those other folios is precisely what the "folio != pmd_folio((*pmd)" check (and the "risk of replacing the wrong folio" comment a few lines above it) is for." BUG: unable to handle page fault for address: ffffea60001db008 CPU: 0 UID: 0 PID: 2199114 Comm: tee Not tainted 6.14.0+ #4 NONE Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:split_huge_pmd_locked+0x3b5/0x2b60 Call Trace: <TASK> try_to_migrate_one+0x28c/0x3730 rmap_walk_anon+0x4f6/0x770 unmap_folio+0x196/0x1f0 split_huge_page_to_list_to_order+0x9f6/0x1560 deferred_split_scan+0xac5/0x12a0 shrinker_debugfs_scan_write+0x376/0x470 full_proxy_write+0x15c/0x220 vfs_write+0x2fc/0xcb0 ksys_write+0x146/0x250 do_syscall_64+0x6a/0x120 entry_SYSCALL_64_after_hwframe+0x76/0x7e The bug is found by syzkaller on an internal kernel, then confirmed on upstream.
A vulnerability was found in the Linux kernel's management of network namespaces. By manipulating the lifecycle of network namespaces, an attacker could exploit this vulnerability to cause a system crash or leak sensitive system memory. Exploitation of this vulnerability requires that a user has access to the system and the ability to create or destroy network namespaces. This typically requires administrative privileges, but could be exposed to an unprivileged user who has control over container lifecycles or a user who has administrative privileges within a container.
Loading 1.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.