GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

RHSA-2025:11810

Vulnerability from csaf_redhat - Published: 2025-07-28 03:13 - Updated: 2026-09-10 12:49
Summary
Red Hat Security Advisory: kernel security update
Severity
Important
Notes
Topic: An update for kernel is now available for Red Hat Enterprise Linux 9.4 Extended Update Support. Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.
Details: The kernel packages contain the Linux kernel, the core of any Linux operating system. Security Fix(es): * kernel: drm/amd/display: Implement bounds check for stream encoder creation in DCN301 (CVE-2024-26660) * kernel: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc (CVE-2021-47185) * kernel: nbd: null check for nla_nest_start (CVE-2024-27025) * kernel: perf/core: Bail out early if the request AUX area is out of bound (CVE-2023-52835) * kernel: firmware: cs_dsp: Fix overflow checking of wmfw header (CVE-2024-41039) * kernel: powerpc/pseries: Whitelist dtl slub object for copying to userspace (CVE-2024-41065) * kernel: usb: xhci: prevent potential failure in handle_tx_event() for Transfer events without TRB (CVE-2024-42226) * kernel: blk-rq-qos: fix crash on rq_qos_wait vs. rq_qos_wake_function race (CVE-2024-50082) * kernel: parport: Proper fix for array out-of-bounds access (CVE-2024-50074) * kernel: ovl: fix UAF in ovl_dentry_update_reval by moving dput() in ovl_link_up (CVE-2025-21887) * kernel: wifi: iwlwifi: limit printed string from FW file (CVE-2025-21905) * kernel: ext4: avoid journaling sb update on error if journal is destroying (CVE-2025-22113) * kernel: ibmvnic: Use kernel helpers for hex dumps (CVE-2025-22104) * kernel: udmabuf: fix a buf size overflow issue during udmabuf creation (CVE-2025-37803) * kernel: sunrpc: handle SVC_GARBAGE during svc auth processing as auth error (CVE-2025-38089) * kernel: net/sched: fix use-after-free in taprio_dev_notifier (CVE-2025-38087) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Terms of Use: This content is licensed under the Creative Commons Attribution 4.0 International License (https://creativecommons.org/licenses/by/4.0/). If you distribute this content, or a modified version of it, you must provide attribution to Red Hat Inc. and provide a link to the original.
CVE-2021-47185

In the Linux kernel, the following vulnerability has been resolved: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc When running ltp testcase(ltp/testcases/kernel/pty/pty04.c) with arm64, there is a soft lockup, which look like this one: Workqueue: events_unbound flush_to_ldisc Call trace: dump_backtrace+0x0/0x1ec show_stack+0x24/0x30 dump_stack+0xd0/0x128 panic+0x15c/0x374 watchdog_timer_fn+0x2b8/0x304 __run_hrtimer+0x88/0x2c0 __hrtimer_run_queues+0xa4/0x120 hrtimer_interrupt+0xfc/0x270 arch_timer_handler_phys+0x40/0x50 handle_percpu_devid_irq+0x94/0x220 __handle_domain_irq+0x88/0xf0 gic_handle_irq+0x84/0xfc el1_irq+0xc8/0x180 slip_unesc+0x80/0x214 [slip] tty_ldisc_receive_buf+0x64/0x80 tty_port_default_receive_buf+0x50/0x90 flush_to_ldisc+0xbc/0x110 process_one_work+0x1d4/0x4b0 worker_thread+0x180/0x430 kthread+0x11c/0x120 In the testcase pty04, The first process call the write syscall to send data to the pty master. At the same time, the workqueue will do the flush_to_ldisc to pop data in a loop until there is no more data left. When the sender and workqueue running in different core, the sender sends data fastly in full time which will result in workqueue doing work in loop for a long time and occuring softlockup in flush_to_ldisc with kernel configured without preempt. So I add need_resched check and cond_resched in the flush_to_ldisc loop to avoid it.

4.4 (Medium)
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
CWE-1050 - Excessive Platform Resource Consumption within a Loop
Affected products
Product Identifier Version Remediation
Unresolved product id: AppStream-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.79.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.79.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.79.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.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-64k-debuginfo-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-64k-devel-0:5.14.0-427.79.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.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.79.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.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-devel-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-devel-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debug-devel-0:5.14.0-427.79.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.79.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.79.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.79.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.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.79.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.79.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.79.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.79.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.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-devel-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-devel-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-devel-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-devel-0:5.14.0-427.79.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.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-devel-matched-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-devel-matched-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-devel-matched-0:5.14.0-427.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-doc-0:5.14.0-427.79.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.79.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.79.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.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-rt-debuginfo-0:5.14.0-427.79.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.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.79.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.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:kernel-zfcpdump-devel-0:5.14.0-427.79.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.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:perf-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:perf-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:perf-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:perf-0:5.14.0-427.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.79.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.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:rtla-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:rtla-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:rtla-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:rtla-0:5.14.0-427.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:rv-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:rv-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:rv-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: AppStream-9.4.0.Z.EUS:rv-0:5.14.0-427.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:bpftool-0:7.3.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:bpftool-0:7.3.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:bpftool-0:7.3.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:bpftool-0:7.3.0-427.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-0:5.14.0-427.79.1.el9_4.src —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-0:5.14.0-427.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-64k-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-64k-core-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-64k-debug-0:5.14.0-427.79.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.79.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.79.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.79.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.79.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.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-64k-debuginfo-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-64k-modules-0:5.14.0-427.79.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.79.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.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-abi-stablelists-0:5.14.0-427.79.1.el9_4.noarch —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-core-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-core-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-core-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-core-0:5.14.0-427.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-0:5.14.0-427.79.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.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-core-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-core-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-core-0:5.14.0-427.79.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.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.79.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.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-modules-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-modules-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debug-modules-0:5.14.0-427.79.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.79.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.79.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.79.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.79.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.79.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.79.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.79.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.79.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.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.79.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.79.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.79.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.79.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.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-0:5.14.0-427.79.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.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-core-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-core-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-core-0:5.14.0-427.79.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.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-extra-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-extra-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-modules-extra-0:5.14.0-427.79.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.79.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.79.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.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-rt-debuginfo-0:5.14.0-427.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-0:5.14.0-427.79.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.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.79.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.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-libs-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-tools-libs-0:5.14.0-427.79.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.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-zfcpdump-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-zfcpdump-core-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-zfcpdump-debuginfo-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:kernel-zfcpdump-modules-0:5.14.0-427.79.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.79.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.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:python3-perf-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:python3-perf-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:python3-perf-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:python3-perf-0:5.14.0-427.79.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.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.79.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.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:kernel-64k-debuginfo-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debug-debuginfo-0:5.14.0-427.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.79.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.79.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.79.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.79.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.79.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.79.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.79.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.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:kernel-rt-debuginfo-0:5.14.0-427.79.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.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:kernel-tools-debuginfo-0:5.14.0-427.79.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.79.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.79.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.79.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.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:libperf-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:libperf-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:libperf-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:libperf-0:5.14.0-427.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.79.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.79.1.el9_4.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.79.1.el9_4.ppc64le —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.79.1.el9_4.s390x —
Vendor Fix fix
Unresolved product id: CRB-9.4.0.Z.EUS:python3-perf-debuginfo-0:5.14.0-427.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.79.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.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.79.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.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-9.4.0.Z.EUS:kernel-rt-0:5.14.0-427.79.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.79.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.79.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.79.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.79.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.79.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.79.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.79.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.79.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.79.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.79.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.79.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.79.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.79.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.79.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.79.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.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.79.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.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: RT-9.4.0.Z.EUS:bpftool-debuginfo-0:7.3.0-427.79.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.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: RT-9.4.0.Z.EUS:kernel-debuginfo-0:5.14.0-427.79.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.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: RT-9.4.0.Z.EUS:kernel-rt-0:5.14.0-427.79.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.79.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.79.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.79.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.79.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.79.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.79.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.79.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.79.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.79.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.79.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.79.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.79.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.79.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.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: RT-9.4.0.Z.EUS:libperf-debuginfo-0:5.14.0-427.79.1.el9_4.x86_64 —
Vendor Fix fix
Unresolved product id: RT-9.4.0.Z.EUS:perf-debuginfo-0:5.14.0-427.79.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.79.1.el9_4.x86_64 —
Vendor Fix fix
Threats
Impact Low
CVE-2023-52835

In the Linux kernel, the following vulnerability has been resolved: perf/core: Bail out early if the request AUX area is out of bound When perf-record with a large AUX area, e.g 4GB, it fails with: #perf record -C 0 -m ,4G -e arm_spe_0// -- sleep 1 failed to mmap with 12 (Cannot allocate memory) and it reveals a WARNING with __alloc_pages(): ------------[ cut here ]------------ WARNING: CPU: 44 PID: 17573 at mm/page_alloc.c:5568 __alloc_pages+0x1ec/0x248 Call trace: __alloc_pages+0x1ec/0x248 __kmalloc_large_node+0xc0/0x1f8 __kmalloc_node+0x134/0x1e8 rb_alloc_aux+0xe0/0x298 perf_mmap+0x440/0x660 mmap_region+0x308/0x8a8 do_mmap+0x3c0/0x528 vm_mmap_pgoff+0xf4/0x1b8 ksys_mmap_pgoff+0x18c/0x218 __arm64_sys_mmap+0x38/0x58 invoke_syscall+0x50/0x128 el0_svc_common.constprop.0+0x58/0x188 do_el0_svc+0x34/0x50 el0_svc+0x34/0x108 el0t_64_sync_handler+0xb8/0xc0 el0t_64_sync+0x1a4/0x1a8 'rb->aux_pages' allocated by kcalloc() is a pointer array which is used to maintains AUX trace pages. The allocated page for this array is physically contiguous (and virtually contiguous) with an order of 0..MAX_ORDER. If the size of pointer array crosses the limitation set by MAX_ORDER, it reveals a WARNING. So bail out early with -ENOMEM if the request AUX area is out of bound, e.g.: #perf record -C 0 -m ,4G -e arm_spe_0// -- sleep 1 failed to mmap with 12 (Cannot allocate memory)

5.5 (Medium)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE-125 - Out-of-bounds Read
Affected products
Fixed 279 products, the same list as for CVE-2021-47185
Threats
Impact Moderate
CVE-2023-53558

A locking violation was found in the Linux kernel RCU-tasks subsystem's callback list initialization. During system boot, the initialization code calls pr_info() while holding the rtp->cbs_gbl_lock spinlock, causing a potentially sleeping function to be called in atomic context, which results in kernel lockdep warnings and potential deadlock leading to denial of service.

4.7 (Medium)
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE-1322 - Use of Blocking Code in Single-threaded, Non-blocking Context
Affected products
Fixed 279 products, the same list as for CVE-2021-47185
Threats
Impact Moderate
CVE-2024-26660

A vulnerability was found in the DRM/AMD/Display module of the Linux Kernel. An out-of-bounds access exists in the 'stream_enc_regs' array within DCN301, while accessing the array with 'eng_id,’ could lead to an out-of-bounds access beyond its four-element size, which can cause a system crash.

4.4 (Medium)
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
CWE-125 - Out-of-bounds Read
Affected products
Fixed 279 products, the same list as for CVE-2021-47185
Threats
Impact Moderate
CVE-2024-27025

In the Linux kernel, the following vulnerability has been resolved: nbd: null check for nla_nest_start The Linux kernel CVE team has assigned CVE-2024-27025 to this issue. Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024050107-CVE-2024-27025-babd@gregkh/T

5.5 (Medium)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE-476 - NULL Pointer Dereference
Affected products
Fixed 279 products, the same list as for CVE-2021-47185
Threats
Impact Low
CVE-2024-41039

A vulnerability was found in the Linux kernel's firmware driver cs_dsp.c, where a buffer overflow is possible in the wmfw header due to insufficient buffer size checks. The issue stems from the size of one of the structs that the code checks, the wmfw_adsp?_sizes struct, which can vary depending on whether the firmware used is ADSP1 or ADSP2 and Halo Core. In the second case, the wmfw_adsp2_sizes struct is 4 bytes longer, which can cause a buffer overflow, potentially leading to undefined behavior in the system.

5.2 (Medium)
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:H
CWE-122 - Heap-based Buffer Overflow
Affected products
Fixed 279 products, the same list as for CVE-2021-47185
Threats
Impact Moderate
CVE-2024-41065

In the Linux kernel, the following vulnerability has been resolved: powerpc/pseries: Whitelist dtl slub object for copying to userspace Reading the dispatch trace log from /sys/kernel/debug/powerpc/dtl/cpu-* results in a BUG() when the config CONFIG_HARDENED_USERCOPY is enabled as shown below. kernel BUG at mm/usercopy.c:102! Oops: Exception in kernel mode, sig: 5 [#1] LE PAGE_SIZE=64K MMU=Radix SMP NR_CPUS=2048 NUMA pSeries Modules linked in: xfs libcrc32c dm_service_time sd_mod t10_pi sg ibmvfc scsi_transport_fc ibmveth pseries_wdt dm_multipath dm_mirror dm_region_hash dm_log dm_mod fuse CPU: 27 PID: 1815 Comm: python3 Not tainted 6.10.0-rc3 #85 Hardware name: IBM,9040-MRX POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1060.00 (NM1060_042) hv:phyp pSeries NIP: c0000000005d23d4 LR: c0000000005d23d0 CTR: 00000000006ee6f8 REGS: c000000120c078c0 TRAP: 0700 Not tainted (6.10.0-rc3) MSR: 8000000000029033 <SF,EE,ME,IR,DR,RI,LE> CR: 2828220f XER: 0000000e CFAR: c0000000001fdc80 IRQMASK: 0 [ ... GPRs omitted ... ] NIP [c0000000005d23d4] usercopy_abort+0x78/0xb0 LR [c0000000005d23d0] usercopy_abort+0x74/0xb0 Call Trace: usercopy_abort+0x74/0xb0 (unreliable) __check_heap_object+0xf8/0x120 check_heap_object+0x218/0x240 __check_object_size+0x84/0x1a4 dtl_file_read+0x17c/0x2c4 full_proxy_read+0x8c/0x110 vfs_read+0xdc/0x3a0 ksys_read+0x84/0x144 system_call_exception+0x124/0x330 system_call_vectored_common+0x15c/0x2ec --- interrupt: 3000 at 0x7fff81f3ab34 Commit 6d07d1cd300f ("usercopy: Restrict non-usercopy caches to size 0") requires that only whitelisted areas in slab/slub objects can be copied to userspace when usercopy hardening is enabled using CONFIG_HARDENED_USERCOPY. Dtl contains hypervisor dispatch events which are expected to be read by privileged users. Hence mark this safe for user access. Specify useroffset=0 and usersize=DISPATCH_LOG_BYTES to whitelist the entire object.

4.4 (Medium)
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
CWE-99 - Improper Control of Resource Identifiers ('Resource Injection')
Affected products
Fixed 279 products, the same list as for CVE-2021-47185
Threats
Impact Low
CVE-2024-42226

In the Linux kernel, the following vulnerability has been resolved: usb: xhci: prevent potential failure in handle_tx_event() for Transfer events without TRB Some transfer events don't always point to a TRB, and consequently don't have a endpoint ring. In these cases, function handle_tx_event() should not proceed, because if 'ep->skip' is set, the pointer to the endpoint ring is used. To prevent a potential failure and make the code logical, return after checking the completion code for a Transfer event without TRBs.

5.5 (Medium)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE-822 - Untrusted Pointer Dereference
Affected products
Fixed 279 products, the same list as for CVE-2021-47185
Threats
Impact Moderate
CVE-2024-50074

An out-of-bounds array access memory flaw was found in the Linux kernel. When snprintf() returns the would-be-printed size, not the actual output size, the length calculation can still go over the given limit and cause an overflow, resulting in loss of availability of the system.

5.5 (Medium)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE-125 - Out-of-bounds Read
Affected products
Fixed 279 products, the same list as for CVE-2021-47185
Threats
Impact Moderate
CVE-2024-50082

In the Linux kernel, the following vulnerability has been resolved: blk-rq-qos: fix crash on rq_qos_wait vs. rq_qos_wake_function race We're seeing crashes from rq_qos_wake_function that look like this: BUG: unable to handle page fault for address: ffffafe180a40084 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD 100000067 P4D 100000067 PUD 10027c067 PMD 10115d067 PTE 0 Oops: Oops: 0002 [#1] PREEMPT SMP PTI CPU: 17 UID: 0 PID: 0 Comm: swapper/17 Not tainted 6.12.0-rc3-00013-geca631b8fe80 #11 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 RIP: 0010:_raw_spin_lock_irqsave+0x1d/0x40 Code: 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 0f 1f 44 00 00 41 54 9c 41 5c fa 65 ff 05 62 97 30 4c 31 c0 ba 01 00 00 00 <f0> 0f b1 17 75 0a 4c 89 e0 41 5c c3 cc cc cc cc 89 c6 e8 2c 0b 00 RSP: 0018:ffffafe180580ca0 EFLAGS: 00010046 RAX: 0000000000000000 RBX: ffffafe180a3f7a8 RCX: 0000000000000011 RDX: 0000000000000001 RSI: 0000000000000003 RDI: ffffafe180a40084 RBP: 0000000000000000 R08: 00000000001e7240 R09: 0000000000000011 R10: 0000000000000028 R11: 0000000000000888 R12: 0000000000000002 R13: ffffafe180a40084 R14: 0000000000000000 R15: 0000000000000003 FS: 0000000000000000(0000) GS:ffff9aaf1f280000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffafe180a40084 CR3: 000000010e428002 CR4: 0000000000770ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: <IRQ> try_to_wake_up+0x5a/0x6a0 rq_qos_wake_function+0x71/0x80 __wake_up_common+0x75/0xa0 __wake_up+0x36/0x60 scale_up.part.0+0x50/0x110 wb_timer_fn+0x227/0x450 ... So rq_qos_wake_function() calls wake_up_process(data->task), which calls try_to_wake_up(), which faults in raw_spin_lock_irqsave(&p->pi_lock). p comes from data->task, and data comes from the waitqueue entry, which is stored on the waiter's stack in rq_qos_wait(). Analyzing the core dump with drgn, I found that the waiter had already woken up and moved on to a completely unrelated code path, clobbering what was previously data->task. Meanwhile, the waker was passing the clobbered garbage in data->task to wake_up_process(), leading to the crash. What's happening is that in between rq_qos_wake_function() deleting the waitqueue entry and calling wake_up_process(), rq_qos_wait() is finding that it already got a token and returning. The race looks like this: rq_qos_wait() rq_qos_wake_function() ============================================================== prepare_to_wait_exclusive() data->got_token = true; list_del_init(&curr->entry); if (data.got_token) break; finish_wait(&rqw->wait, &data.wq); ^- returns immediately because list_empty_careful(&wq_entry->entry) is true ... return, go do something else ... wake_up_process(data->task) (NO LONGER VALID!)-^ Normally, finish_wait() is supposed to synchronize against the waker. But, as noted above, it is returning immediately because the waitqueue entry has already been removed from the waitqueue. The bug is that rq_qos_wake_function() is accessing the waitqueue entry AFTER deleting it. Note that autoremove_wake_function() wakes the waiter and THEN deletes the waitqueue entry, which is the proper order. Fix it by swapping the order. We also need to use list_del_init_careful() to match the list_empty_careful() in finish_wait().

4.1 (Medium)
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
CWE-362 - Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Affected products
Fixed 279 products, the same list as for CVE-2021-47185
Threats
Impact Low
CVE-2025-21887

A use after free vulnerability exists in the linux kernel such that dput(upper) is being called before ovl_dentry_update_reval(), while upper->d_flags was still accessed in ovl_dentry_remote().

7.1 (High)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
CWE-416 - Use After Free
Affected products
Fixed 279 products, the same list as for CVE-2021-47185
Threats
Impact Moderate
CVE-2025-21905

In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: limit printed string from FW file There's no guarantee here that the file is always with a NUL-termination, so reading the string may read beyond the end of the TLV. If that's the last TLV in the file, it can perhaps even read beyond the end of the file buffer. Fix that by limiting the print format to the size of the buffer we have.

6.0 (Medium)
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:H
CWE-125 - Out-of-bounds Read
Affected products
Fixed 279 products, the same list as for CVE-2021-47185
Threats
Impact Moderate
CVE-2025-22104

In the Linux kernel, the following vulnerability has been resolved: ibmvnic: Use kernel helpers for hex dumps Previously, when the driver was printing hex dumps, the buffer was cast to an 8 byte long and printed using string formatters. If the buffer size was not a multiple of 8 then a read buffer overflow was possible. Therefore, create a new ibmvnic function that loops over a buffer and calls hex_dump_to_buffer instead. This patch address KASAN reports like the one below: ibmvnic 30000003 env3: Login Buffer: ibmvnic 30000003 env3: 01000000af000000 <...> ibmvnic 30000003 env3: 2e6d62692e736261 ibmvnic 30000003 env3: 65050003006d6f63 ================================================================== BUG: KASAN: slab-out-of-bounds in ibmvnic_login+0xacc/0xffc [ibmvnic] Read of size 8 at addr c0000001331a9aa8 by task ip/17681 <...> Allocated by task 17681: <...> ibmvnic_login+0x2f0/0xffc [ibmvnic] ibmvnic_open+0x148/0x308 [ibmvnic] __dev_open+0x1ac/0x304 <...> The buggy address is located 168 bytes inside of allocated 175-byte region [c0000001331a9a00, c0000001331a9aaf) <...> ================================================================= ibmvnic 30000003 env3: 000000000033766e

7.1 (High)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
CWE-120 - Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Affected products
Fixed 279 products, the same list as for CVE-2021-47185
Threats
Impact Moderate
CVE-2025-22113

In the Linux kernel, the following vulnerability has been resolved: ext4: avoid journaling sb update on error if journal is destroying Presently we always BUG_ON if trying to start a transaction on a journal marked with JBD2_UNMOUNT, since this should never happen. However, while ltp running stress tests, it was observed that in case of some error handling paths, it is possible for update_super_work to start a transaction after the journal is destroyed eg: (umount) ext4_kill_sb kill_block_super generic_shutdown_super sync_filesystem /* commits all txns */ evict_inodes /* might start a new txn */ ext4_put_super flush_work(&sbi->s_sb_upd_work) /* flush the workqueue */ jbd2_journal_destroy journal_kill_thread journal->j_flags |= JBD2_UNMOUNT; jbd2_journal_commit_transaction jbd2_journal_get_descriptor_buffer jbd2_journal_bmap ext4_journal_bmap ext4_map_blocks ... ext4_inode_error ext4_handle_error schedule_work(&sbi->s_sb_upd_work) /* work queue kicks in */ update_super_work jbd2_journal_start start_this_handle BUG_ON(journal->j_flags & JBD2_UNMOUNT) Hence, introduce a new mount flag to indicate journal is destroying and only do a journaled (and deferred) update of sb if this flag is not set. Otherwise, just fallback to an un-journaled commit. Further, in the journal destroy path, we have the following sequence: 1. Set mount flag indicating journal is destroying 2. force a commit and wait for it 3. flush pending sb updates This sequence is important as it ensures that, after this point, there is no sb update that might be journaled so it is safe to update the sb outside the journal. (To avoid race discussed in 2d01ddc86606) Also, we don't need a similar check in ext4_grp_locked_error since it is only called from mballoc and AFAICT it would be always valid to schedule work here.

7.1 (High)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
CWE-99 - Improper Control of Resource Identifiers ('Resource Injection')
Affected products
Fixed 279 products, the same list as for CVE-2021-47185
Threats
Impact Moderate
CVE-2025-37803

A buffer-overflow vulnerability was found in the Linux kernel's udmabuf driver. The flaw occurs in the `udmabuf_create()` function, which calculates the page count limit (`pglimit`) using the variable `size_limit_mb`. This size variable can be misinterpreted as either 32-bit or 64-bit, resulting in incorrect page limit checks and allocating a larger DMA buffer than permitted. This issue can lead to memory corruption, system instability, and a denial of service.

7.3 (High)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H
CWE-120 - Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Affected products
Fixed 279 products, the same list as for CVE-2021-47185
Threats
Impact Moderate
CVE-2025-38087

In the Linux kernel, the following vulnerability has been resolved: net/sched: fix use-after-free in taprio_dev_notifier Since taprio’s taprio_dev_notifier() isn’t protected by an RCU read-side critical section, a race with advance_sched() can lead to a use-after-free. Adding rcu_read_lock() inside taprio_dev_notifier() prevents this.

7.8 (High)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE-416 - Use After Free
Affected products
Fixed 279 products, the same list as for CVE-2021-47185
Threats
Impact Moderate
CVE-2025-38089

A flaw was found in the Linux kernel, where a specially crafted RPC packet could cause data corruption or trigger a system panic. This flaw allows a remote attacker who can make RPC calls to send an intentionally malformed packet, potentially compromising system integrity or causing a denial of service (DoS).

7.1 (High)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
CWE-754 - Improper Check for Unusual or Exceptional Conditions
Affected products
Fixed 279 products, the same list as for CVE-2021-47185
Threats
Impact Important
References
URL Category
https://access.redhat.com/errata/RHSA-2025:11810 self
https://access.redhat.com/security/updates/classi… external
https://bugzilla.redhat.com/show_bug.cgi?id=2272782 external
https://bugzilla.redhat.com/show_bug.cgi?id=2274624 external
https://bugzilla.redhat.com/show_bug.cgi?id=2278484 external
https://bugzilla.redhat.com/show_bug.cgi?id=2282735 external
https://bugzilla.redhat.com/show_bug.cgi?id=2300408 external
https://bugzilla.redhat.com/show_bug.cgi?id=2300440 external
https://bugzilla.redhat.com/show_bug.cgi?id=2301544 external
https://bugzilla.redhat.com/show_bug.cgi?id=2322308 external
https://bugzilla.redhat.com/show_bug.cgi?id=2322310 external
https://bugzilla.redhat.com/show_bug.cgi?id=2355405 external
https://bugzilla.redhat.com/show_bug.cgi?id=2356613 external
https://bugzilla.redhat.com/show_bug.cgi?id=2360212 external
https://bugzilla.redhat.com/show_bug.cgi?id=2360265 external
https://bugzilla.redhat.com/show_bug.cgi?id=2365013 external
https://bugzilla.redhat.com/show_bug.cgi?id=2375529 external
https://bugzilla.redhat.com/show_bug.cgi?id=2375531 external
https://security.access.redhat.com/data/csaf/v2/a… self
https://access.redhat.com/security/cve/CVE-2021-47185 self
https://bugzilla.redhat.com/show_bug.cgi?id=2274624 external
https://www.cve.org/CVERecord?id=CVE-2021-47185 external
https://nvd.nist.gov/vuln/detail/CVE-2021-47185 external
https://lore.kernel.org/linux-cve-announce/202404… external
https://access.redhat.com/security/cve/CVE-2023-52835 self
https://bugzilla.redhat.com/show_bug.cgi?id=2282735 external
https://www.cve.org/CVERecord?id=CVE-2023-52835 external
https://nvd.nist.gov/vuln/detail/CVE-2023-52835 external
https://lore.kernel.org/linux-cve-announce/202405… external
https://access.redhat.com/security/cve/CVE-2023-53558 self
https://bugzilla.redhat.com/show_bug.cgi?id=2401543 external
https://www.cve.org/CVERecord?id=CVE-2023-53558 external
https://nvd.nist.gov/vuln/detail/CVE-2023-53558 external
https://lore.kernel.org/linux-cve-announce/202510… external
https://access.redhat.com/security/cve/CVE-2024-26660 self
https://bugzilla.redhat.com/show_bug.cgi?id=2272782 external
https://www.cve.org/CVERecord?id=CVE-2024-26660 external
https://nvd.nist.gov/vuln/detail/CVE-2024-26660 external
https://lore.kernel.org/linux-cve-announce/202404… external
https://access.redhat.com/security/cve/CVE-2024-27025 self
https://bugzilla.redhat.com/show_bug.cgi?id=2278484 external
https://www.cve.org/CVERecord?id=CVE-2024-27025 external
https://nvd.nist.gov/vuln/detail/CVE-2024-27025 external
https://lore.kernel.org/linux-cve-announce/202405… external
https://access.redhat.com/security/cve/CVE-2024-41039 self
https://bugzilla.redhat.com/show_bug.cgi?id=2300408 external
https://www.cve.org/CVERecord?id=CVE-2024-41039 external
https://nvd.nist.gov/vuln/detail/CVE-2024-41039 external
https://lore.kernel.org/linux-cve-announce/202407… external
https://access.redhat.com/security/cve/CVE-2024-41065 self
https://bugzilla.redhat.com/show_bug.cgi?id=2300440 external
https://www.cve.org/CVERecord?id=CVE-2024-41065 external
https://nvd.nist.gov/vuln/detail/CVE-2024-41065 external
https://lore.kernel.org/linux-cve-announce/202407… external
https://access.redhat.com/security/cve/CVE-2024-42226 self
https://bugzilla.redhat.com/show_bug.cgi?id=2301544 external
https://www.cve.org/CVERecord?id=CVE-2024-42226 external
https://nvd.nist.gov/vuln/detail/CVE-2024-42226 external
https://lore.kernel.org/linux-cve-announce/202407… external
https://access.redhat.com/security/cve/CVE-2024-50074 self
https://bugzilla.redhat.com/show_bug.cgi?id=2322310 external
https://www.cve.org/CVERecord?id=CVE-2024-50074 external
https://nvd.nist.gov/vuln/detail/CVE-2024-50074 external
https://lore.kernel.org/linux-cve-announce/202410… external
https://access.redhat.com/security/cve/CVE-2024-50082 self
https://bugzilla.redhat.com/show_bug.cgi?id=2322308 external
https://www.cve.org/CVERecord?id=CVE-2024-50082 external
https://nvd.nist.gov/vuln/detail/CVE-2024-50082 external
https://lore.kernel.org/linux-cve-announce/202410… external
https://access.redhat.com/security/cve/CVE-2025-21887 self
https://bugzilla.redhat.com/show_bug.cgi?id=2355405 external
https://www.cve.org/CVERecord?id=CVE-2025-21887 external
https://nvd.nist.gov/vuln/detail/CVE-2025-21887 external
https://lore.kernel.org/linux-cve-announce/202503… external
https://access.redhat.com/security/cve/CVE-2025-21905 self
https://bugzilla.redhat.com/show_bug.cgi?id=2356613 external
https://www.cve.org/CVERecord?id=CVE-2025-21905 external
https://nvd.nist.gov/vuln/detail/CVE-2025-21905 external
https://lore.kernel.org/linux-cve-announce/202504… external
https://access.redhat.com/security/cve/CVE-2025-22104 self
https://bugzilla.redhat.com/show_bug.cgi?id=2360265 external
https://www.cve.org/CVERecord?id=CVE-2025-22104 external
https://nvd.nist.gov/vuln/detail/CVE-2025-22104 external
https://lore.kernel.org/linux-cve-announce/202504… external
https://access.redhat.com/security/cve/CVE-2025-22113 self
https://bugzilla.redhat.com/show_bug.cgi?id=2360212 external
https://www.cve.org/CVERecord?id=CVE-2025-22113 external
https://nvd.nist.gov/vuln/detail/CVE-2025-22113 external
https://lore.kernel.org/linux-cve-announce/202504… external
https://access.redhat.com/security/cve/CVE-2025-37803 self
https://bugzilla.redhat.com/show_bug.cgi?id=2365013 external
https://www.cve.org/CVERecord?id=CVE-2025-37803 external
https://nvd.nist.gov/vuln/detail/CVE-2025-37803 external
https://lore.kernel.org/linux-cve-announce/202505… external
https://access.redhat.com/security/cve/CVE-2025-38087 self
https://bugzilla.redhat.com/show_bug.cgi?id=2375531 external
https://www.cve.org/CVERecord?id=CVE-2025-38087 external
https://nvd.nist.gov/vuln/detail/CVE-2025-38087 external
https://lore.kernel.org/linux-cve-announce/202506… external
https://access.redhat.com/security/cve/CVE-2025-38089 self
https://bugzilla.redhat.com/show_bug.cgi?id=2375529 external
https://www.cve.org/CVERecord?id=CVE-2025-38089 external
https://nvd.nist.gov/vuln/detail/CVE-2025-38089 external
https://lore.kernel.org/linux-cve-announce/202506… external
To clipboard 

Loading 1.6 MB of JSON…



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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.


Detection rules are retrieved from Rulezet.


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.