RHSA-2026:18134

Vulnerability from csaf_redhat - Published: 2026-05-19 09:04 - Updated: 2026-11-13 12:47
Summary
Red Hat Security Advisory: kernel security update
Severity
Moderate
Notes
Topic: An update for kernel is now available for Red Hat Enterprise Linux 10. Red Hat Product Security has rated this update as having a security impact of Moderate. 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: tcp_bpf: Fix the sk_mem_uncharge logic in tcp_bpf_sendmsg (CVE-2024-56633) * kernel: KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop (CVE-2025-21839) * kernel: block: fix resource leak in blk_register_queue() error path (CVE-2025-37980) * kernel: dmaengine: idxd: fix memory leak in error handling path of idxd_alloc (CVE-2025-38015) * kernel: espintcp: remove encap socket caching to avoid reference leak (CVE-2025-38097) * kernel: bpf: fix ktls panic with sockmap (CVE-2025-38166) * kernel: bpf: Check rcu_read_lock_trace_held() in bpf_map_lookup_percpu_elem() (CVE-2025-38202) * kernel: bpf: Do not include stack ptr register in precision backtracking bookkeeping (CVE-2025-38279) * kernel: ring-buffer: Do not trigger WARN_ON() due to a commit_overrun (CVE-2025-38267) * kernel: phy: qcom-qmp-usb: Fix an NULL vs IS_ERR() bug (CVE-2025-38275) * kernel: ftrace: Fix UAF when lookup kallsym after ftrace disabled (CVE-2025-38346) * kernel: ACPICA: fix acpi operand cache leak in dswstate.c (CVE-2025-38345) * kernel: nvmet: fix memory leak of bio integrity (CVE-2025-38405) * kernel: netfilter: flowtable: account for Ethernet header in nf_flow_pppoe_proto() (CVE-2025-38441) * kernel: net: vlan: fix VLAN 0 refcount imbalance of toggling filtering during runtime (CVE-2025-38470) * kernel: fs: writeback: fix use-after-free in __mark_inode_dirty() (CVE-2025-39866) * kernel: PCI/AER: Avoid NULL pointer dereference in aer_ratelimit() (CVE-2025-40034) * kernel: dm: fix NULL pointer dereference in __dm_suspend() (CVE-2025-40134) * kernel: Revert "NFSD: Remove the cap on number of operations per NFSv4 COMPOUND" (CVE-2025-40210) * kernel: Linux kernel MPTCP: Privilege escalation or denial of service via use-after-free in timer handling (CVE-2025-40257) * kernel: smb: client: fix potential cfid UAF in smb2_query_info_compound (CVE-2025-40320) * kernel: wifi: mac80211_hwsim: fix typo in frequency notification (CVE-2026-23040) * kernel: Kernel: Privilege escalation or denial of service in nf_tables via inverted element activity check (CVE-2026-23111) * kernel: Linux kernel: Denial of Service in ice driver due to race condition during VSI rebuild (CVE-2026-23210) * kernel: Linux kernel: Denial of service and memory corruption in RDMA umad (CVE-2026-23243) 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. Additional Changes: For detailed information on changes in this release, see the Red Hat Enterprise Linux 10 Release Notes linked from 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-2024-56633

A flaw was found in the Linux kernel's BPF (Berkeley Packet Filter) networking subsystem. When processing socket message redirection or packet drops configured with specific byte limits, the kernel fails to properly balance socket memory accounting. A local user with permissions to configure BPF socket redirection can exploit this flaw to cause memory tracking inconsistencies and kernel warnings, potentially leading to a Denial of Service (DoS).

5.5 (Medium)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE-99 - Improper Control of Resource Identifiers
Affected products
Product Identifier Version Remediation
Unresolved product id: AppStream-10.2.GA:kernel-64k-debug-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-64k-debug-devel-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-64k-debug-devel-matched-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-64k-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-64k-devel-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-64k-devel-matched-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-debug-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-debug-debuginfo-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-debug-debuginfo-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-debug-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-debug-devel-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-debug-devel-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-debug-devel-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-debug-devel-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-debug-devel-matched-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-debug-devel-matched-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-debug-devel-matched-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-debug-devel-matched-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-debuginfo-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-debuginfo-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-debuginfo-common-aarch64-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-debuginfo-common-ppc64le-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-debuginfo-common-s390x-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-debuginfo-common-x86_64-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-devel-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-devel-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-devel-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-devel-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-devel-matched-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-devel-matched-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-devel-matched-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-devel-matched-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-doc-0:6.12.0-211.7.1.el10_2.noarch —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-rt-64k-debug-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-rt-64k-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-rt-debug-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-rt-debug-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-rt-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-rt-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-tools-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-tools-debuginfo-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-tools-debuginfo-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-tools-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-zfcpdump-debuginfo-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-zfcpdump-devel-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:kernel-zfcpdump-devel-matched-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:libperf-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:libperf-debuginfo-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:libperf-debuginfo-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:libperf-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:perf-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:perf-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:perf-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:perf-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:perf-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:perf-debuginfo-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:perf-debuginfo-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:perf-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:python3-perf-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:python3-perf-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:python3-perf-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:python3-perf-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:python3-perf-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:python3-perf-debuginfo-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:python3-perf-debuginfo-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:python3-perf-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:rtla-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:rtla-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:rtla-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:rtla-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:rv-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:rv-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:rv-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: AppStream-10.2.GA:rv-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-0:6.12.0-211.7.1.el10_2.src —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-64k-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-64k-core-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-64k-debug-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-64k-debug-core-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-64k-debug-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-64k-debug-modules-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-64k-debug-modules-core-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-64k-debug-modules-extra-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-64k-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-64k-modules-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-64k-modules-core-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-64k-modules-extra-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-abi-stablelists-0:6.12.0-211.7.1.el10_2.noarch —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-core-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-core-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-core-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-core-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-core-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-core-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-core-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-core-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-debuginfo-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-debuginfo-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-modules-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-modules-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-modules-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-modules-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-modules-core-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-modules-core-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-modules-core-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-modules-core-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-modules-extra-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-modules-extra-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-modules-extra-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-modules-extra-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debug-uki-virt-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debuginfo-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debuginfo-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debuginfo-common-aarch64-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debuginfo-common-ppc64le-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debuginfo-common-s390x-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-debuginfo-common-x86_64-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-modules-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-modules-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-modules-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-modules-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-modules-core-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-modules-core-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-modules-core-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-modules-core-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-modules-extra-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-modules-extra-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-modules-extra-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-modules-extra-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-modules-extra-matched-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-modules-extra-matched-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-modules-extra-matched-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-modules-extra-matched-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-rt-64k-debug-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-rt-64k-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-rt-debug-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-rt-debug-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-rt-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-rt-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-tools-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-tools-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-tools-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-tools-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-tools-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-tools-debuginfo-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-tools-debuginfo-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-tools-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-tools-libs-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-tools-libs-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-tools-libs-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-uki-virt-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-uki-virt-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-uki-virt-addons-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-uki-virt-addons-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-zfcpdump-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-zfcpdump-core-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-zfcpdump-debuginfo-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-zfcpdump-modules-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-zfcpdump-modules-core-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:kernel-zfcpdump-modules-extra-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:libperf-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:libperf-debuginfo-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:libperf-debuginfo-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:libperf-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:perf-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:perf-debuginfo-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:perf-debuginfo-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:perf-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:python3-perf-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:python3-perf-debuginfo-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:python3-perf-debuginfo-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: BaseOS-10.2.GA:python3-perf-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-64k-debug-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-64k-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-debug-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-debug-debuginfo-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-debug-debuginfo-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-debug-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-debuginfo-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-debuginfo-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-debuginfo-common-aarch64-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-debuginfo-common-ppc64le-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-debuginfo-common-s390x-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-debuginfo-common-x86_64-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-rt-64k-debug-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-rt-64k-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-rt-debug-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-rt-debug-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-rt-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-rt-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-tools-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-tools-debuginfo-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-tools-debuginfo-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-tools-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-tools-libs-devel-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-tools-libs-devel-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-tools-libs-devel-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:kernel-zfcpdump-debuginfo-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:libperf-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:libperf-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:libperf-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:libperf-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:libperf-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:libperf-debuginfo-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:libperf-debuginfo-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:libperf-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:perf-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:perf-debuginfo-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:perf-debuginfo-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:perf-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:python3-perf-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:python3-perf-debuginfo-0:6.12.0-211.7.1.el10_2.ppc64le —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:python3-perf-debuginfo-0:6.12.0-211.7.1.el10_2.s390x —
Vendor Fix fix
Unresolved product id: CRB-10.2.GA:python3-perf-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-10.2.GA:kernel-debug-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-10.2.GA:kernel-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-10.2.GA:kernel-debuginfo-common-x86_64-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-10.2.GA:kernel-rt-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-10.2.GA:kernel-rt-core-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-10.2.GA:kernel-rt-debug-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-10.2.GA:kernel-rt-debug-core-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-10.2.GA:kernel-rt-debug-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-10.2.GA:kernel-rt-debug-devel-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-10.2.GA:kernel-rt-debug-modules-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-10.2.GA:kernel-rt-debug-modules-core-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-10.2.GA:kernel-rt-debug-modules-extra-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-10.2.GA:kernel-rt-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-10.2.GA:kernel-rt-devel-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-10.2.GA:kernel-rt-modules-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-10.2.GA:kernel-rt-modules-core-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-10.2.GA:kernel-rt-modules-extra-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-10.2.GA:kernel-tools-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-10.2.GA:libperf-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-10.2.GA:perf-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: NFV-10.2.GA:python3-perf-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-64k-debug-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-64k-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-debug-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-debug-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-debuginfo-common-aarch64-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-debuginfo-common-x86_64-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-64k-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-64k-core-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-64k-debug-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-64k-debug-core-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-64k-debug-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-64k-debug-devel-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-64k-debug-modules-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-64k-debug-modules-core-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-64k-debug-modules-extra-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-64k-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-64k-devel-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-64k-modules-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-64k-modules-core-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-64k-modules-extra-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-core-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-core-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-debug-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-debug-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-debug-core-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-debug-core-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-debug-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-debug-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-debug-devel-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-debug-devel-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-debug-modules-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-debug-modules-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-debug-modules-core-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-debug-modules-core-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-debug-modules-extra-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-debug-modules-extra-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-devel-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-devel-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-modules-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-modules-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-modules-core-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-modules-core-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-modules-extra-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-rt-modules-extra-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-tools-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:kernel-tools-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:libperf-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:libperf-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:perf-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:perf-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:python3-perf-debuginfo-0:6.12.0-211.7.1.el10_2.aarch64 —
Vendor Fix fix
Unresolved product id: RT-10.2.GA:python3-perf-debuginfo-0:6.12.0-211.7.1.el10_2.x86_64 —
Vendor Fix fix
Threats
Impact Moderate
CVE-2025-21839

A flaw was found in the Linux kernel's KVM (Kernel-based Virtual Machine) subsystem. An authenticated user within a guest virtual machine can cause a denial of service (DoS) or register state corruption, particularly in nested virtualization environments. When a guest updates its debug registers, KVM can overwrite the hardware register with an outdated value during certain virtual machine exits before saving the updated state. This state desynchronization can disrupt guest execution or cause the guest operating system to crash.

5.5 (Medium)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE-665 - Improper Initialization
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Moderate
CVE-2025-30156

A flaw was found in the CephX authentication protocol used by Ceph, a distributed storage system. CephX uses AES-128-CBC encryption with a hardcoded initialization vector and no message authentication (HMAC), making it vulnerable to the same class of unauthenticated-encryption attacks that compromised Kerberos 4 as documented in MIT's 2004 PERILS paper. An attacker who has compromised a single low-privilege CephX entity key can use the Ceph monitor as an encryption oracle by requesting tickets for specially-named entity identities over a standard network connection. The monitor encrypts these attacker-controlled names into ciphertext blocks which, due to absent integrity protection, can be spliced into forged credentials for privileged entities such as OSDs, MDSs, and MGRs. This grants cluster-wide access including data reads, data corruption, and full administrative control.

8.7 (High)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
CWE-1204 - Generation of Weak Initialization Vector (IV)
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Important
CVE-2025-37980

In the Linux kernel, the following vulnerability has been resolved: block: fix resource leak in blk_register_queue() error path When registering a queue fails after blk_mq_sysfs_register() is successful but the function later encounters an error, we need to clean up the blk_mq_sysfs resources. Add the missing blk_mq_sysfs_unregister() call in the error path to properly clean up these resources and prevent a memory leak.

3.3 (Low)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
CWE-459 - Incomplete Cleanup
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Low
CVE-2025-38015

In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: fix memory leak in error handling path of idxd_alloc Memory allocated for idxd is not freed if an error occurs during idxd_alloc(). To fix it, free the allocated memory in the reverse order of allocation before exiting the function in case of an error.

5.5 (Medium)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE-772 - Missing Release of Resource after Effective Lifetime
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Moderate
CVE-2025-38097

In the Linux kernel, the following vulnerability has been resolved: espintcp: remove encap socket caching to avoid reference leak The current scheme for caching the encap socket can lead to reference leaks when we try to delete the netns. The reference chain is: xfrm_state -> enacp_sk -> netns Since the encap socket is a userspace socket, it holds a reference on the netns. If we delete the espintcp state (through flush or individual delete) before removing the netns, the reference on the socket is dropped and the netns is correctly deleted. Otherwise, the netns may not be reachable anymore (if all processes within the ns have terminated), so we cannot delete the xfrm state to drop its reference on the socket. This patch results in a small (~2% in my tests) performance regression. A GC-type mechanism could be added for the socket cache, to clear references if the state hasn't been used "recently", but it's a lot more complex than just not caching the socket.

3.3 (Low)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
CWE-772 - Missing Release of Resource after Effective Lifetime
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Low
CVE-2025-38166

A flaw was found in the Linux kernel. A local privileged user can cause a Denial of Service (DoS) by triggering a kernel crash. When a Berkeley Packet Filter (BPF) program attached to a kernel Transport Layer Security (kTLS) socket modifies message data and encounters socket corking, the kernel incorrectly calculates buffer rollback boundaries. This inconsistency triggers a kernel panic, causing the system to crash.

5.5 (Medium)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE-131 - Incorrect Calculation of Buffer Size
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Moderate
CVE-2025-38202

In the Linux kernel, the following vulnerability has been resolved: bpf: Check rcu_read_lock_trace_held() in bpf_map_lookup_percpu_elem() bpf_map_lookup_percpu_elem() helper is also available for sleepable bpf program. When BPF JIT is disabled or under 32-bit host, bpf_map_lookup_percpu_elem() will not be inlined. Using it in a sleepable bpf program will trigger the warning in bpf_map_lookup_percpu_elem(), because the bpf program only holds rcu_read_lock_trace lock. Therefore, add the missed check.

3.3 (Low)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
CWE-414 - Missing Lock Check
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Low
CVE-2025-38267

In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Do not trigger WARN_ON() due to a commit_overrun When reading a memory mapped buffer the reader page is just swapped out with the last page written in the write buffer. If the reader page is the same as the commit buffer (the buffer that is currently being written to) it was assumed that it should never have missed events. If it does, it triggers a WARN_ON_ONCE(). But there just happens to be one scenario where this can legitimately happen. That is on a commit_overrun. A commit overrun is when an interrupt preempts an event being written to the buffer and then the interrupt adds so many new events that it fills and wraps the buffer back to the commit. Any new events would then be dropped and be reported as "missed_events". In this case, the next page to read is the commit buffer and after the swap of the reader page, the reader page will be the commit buffer, but this time there will be missed events and this triggers the following warning: ------------[ cut here ]------------ WARNING: CPU: 2 PID: 1127 at kernel/trace/ring_buffer.c:7357 ring_buffer_map_get_reader+0x49a/0x780 Modules linked in: kvm_intel kvm irqbypass CPU: 2 UID: 0 PID: 1127 Comm: trace-cmd Not tainted 6.15.0-rc7-test-00004-g478bc2824b45-dirty #564 PREEMPT Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:ring_buffer_map_get_reader+0x49a/0x780 Code: 00 00 00 48 89 fe 48 c1 ee 03 80 3c 2e 00 0f 85 ec 01 00 00 4d 3b a6 a8 00 00 00 0f 85 8a fd ff ff 48 85 c0 0f 84 55 fe ff ff <0f> 0b e9 4e fe ff ff be 08 00 00 00 4c 89 54 24 58 48 89 54 24 50 RSP: 0018:ffff888121787dc0 EFLAGS: 00010002 RAX: 00000000000006a2 RBX: ffff888100062800 RCX: ffffffff8190cb49 RDX: ffff888126934c00 RSI: 1ffff11020200a15 RDI: ffff8881010050a8 RBP: dffffc0000000000 R08: 0000000000000000 R09: ffffed1024d26982 R10: ffff888126934c17 R11: ffff8881010050a8 R12: ffff888126934c00 R13: ffff8881010050b8 R14: ffff888101005000 R15: ffff888126930008 FS: 00007f95c8cd7540(0000) GS:ffff8882b576e000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f95c8de4dc0 CR3: 0000000128452002 CR4: 0000000000172ef0 Call Trace: <TASK> ? __pfx_ring_buffer_map_get_reader+0x10/0x10 tracing_buffers_ioctl+0x283/0x370 __x64_sys_ioctl+0x134/0x190 do_syscall_64+0x79/0x1c0 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f95c8de48db Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 00 00 RSP: 002b:00007ffe037ba110 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007ffe037bb2b0 RCX: 00007f95c8de48db RDX: 0000000000000000 RSI: 0000000000005220 RDI: 0000000000000006 RBP: 00007ffe037ba180 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffe037bb6f8 R14: 00007f95c9065000 R15: 00005575c7492c90 </TASK> irq event stamp: 5080 hardirqs last enabled at (5079): [<ffffffff83e0adb0>] _raw_spin_unlock_irqrestore+0x50/0x70 hardirqs last disabled at (5080): [<ffffffff83e0aa83>] _raw_spin_lock_irqsave+0x63/0x70 softirqs last enabled at (4182): [<ffffffff81516122>] handle_softirqs+0x552/0x710 softirqs last disabled at (4159): [<ffffffff815163f7>] __irq_exit_rcu+0x107/0x210 ---[ end trace 0000000000000000 ]--- The above was triggered by running on a kernel with both lockdep and KASAN as well as kmemleak enabled and executing the following command: # perf record -o perf-test.dat -a -- trace-cmd record --nosplice -e all -p function hackbench 50 With perf interjecting a lot of interrupts and trace-cmd enabling all events as well as function tracing, with lockdep, KASAN and kmemleak enabled, it could cause an interrupt preempting an event being written to add enough event ---truncated---

5.5 (Medium)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE-821 - Incorrect Synchronization
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Moderate
CVE-2025-38275

In the Linux kernel, the following vulnerability has been resolved: phy: qcom-qmp-usb: Fix an NULL vs IS_ERR() bug The qmp_usb_iomap() helper function currently returns the raw result of devm_ioremap() for non-exclusive mappings. Since devm_ioremap() may return a NULL pointer and the caller only checks error pointers with IS_ERR(), NULL could bypass the check and lead to an invalid dereference. Fix the issue by checking if devm_ioremap() returns NULL. When it does, qmp_usb_iomap() now returns an error pointer via IOMEM_ERR_PTR(-ENOMEM), ensuring safe and consistent error handling.

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 309 products, the same list as for CVE-2024-56633
Threats
Impact Moderate
CVE-2025-38279

In the Linux kernel, the following vulnerability has been resolved: bpf: Do not include stack ptr register in precision backtracking bookkeeping Yi Lai reported an issue ([1]) where the following warning appears in kernel dmesg: [ 60.643604] verifier backtracking bug [ 60.643635] WARNING: CPU: 10 PID: 2315 at kernel/bpf/verifier.c:4302 __mark_chain_precision+0x3a6c/0x3e10 [ 60.648428] Modules linked in: bpf_testmod(OE) [ 60.650471] CPU: 10 UID: 0 PID: 2315 Comm: test_progs Tainted: G OE 6.15.0-rc4-gef11287f8289-dirty #327 PREEMPT(full) [ 60.654385] Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE [ 60.656682] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 [ 60.660475] RIP: 0010:__mark_chain_precision+0x3a6c/0x3e10 [ 60.662814] Code: 5a 30 84 89 ea e8 c4 d9 01 00 80 3d 3e 7d d8 04 00 0f 85 60 fa ff ff c6 05 31 7d d8 04 01 48 c7 c7 00 58 30 84 e8 c4 06 a5 ff <0f> 0b e9 46 fa ff ff 48 ... [ 60.668720] RSP: 0018:ffff888116cc7298 EFLAGS: 00010246 [ 60.671075] RAX: 54d70e82dfd31900 RBX: ffff888115b65e20 RCX: 0000000000000000 [ 60.673659] RDX: 0000000000000001 RSI: 0000000000000004 RDI: 00000000ffffffff [ 60.676241] RBP: 0000000000000400 R08: ffff8881f6f23bd3 R09: 1ffff1103ede477a [ 60.678787] R10: dffffc0000000000 R11: ffffed103ede477b R12: ffff888115b60ae8 [ 60.681420] R13: 1ffff11022b6cbc4 R14: 00000000fffffff2 R15: 0000000000000001 [ 60.684030] FS: 00007fc2aedd80c0(0000) GS:ffff88826fa8a000(0000) knlGS:0000000000000000 [ 60.686837] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 60.689027] CR2: 000056325369e000 CR3: 000000011088b002 CR4: 0000000000370ef0 [ 60.691623] Call Trace: [ 60.692821] <TASK> [ 60.693960] ? __pfx_verbose+0x10/0x10 [ 60.695656] ? __pfx_disasm_kfunc_name+0x10/0x10 [ 60.697495] check_cond_jmp_op+0x16f7/0x39b0 [ 60.699237] do_check+0x58fa/0xab10 ... Further analysis shows the warning is at line 4302 as below: 4294 /* static subprog call instruction, which 4295 * means that we are exiting current subprog, 4296 * so only r1-r5 could be still requested as 4297 * precise, r0 and r6-r10 or any stack slot in 4298 * the current frame should be zero by now 4299 */ 4300 if (bt_reg_mask(bt) & ~BPF_REGMASK_ARGS) { 4301 verbose(env, "BUG regs %x\n", bt_reg_mask(bt)); 4302 WARN_ONCE(1, "verifier backtracking bug"); 4303 return -EFAULT; 4304 } With the below test (also in the next patch): __used __naked static void __bpf_jmp_r10(void) { asm volatile ( "r2 = 2314885393468386424 ll;" "goto +0;" "if r2 <= r10 goto +3;" "if r1 >= -1835016 goto +0;" "if r2 <= 8 goto +0;" "if r3 <= 0 goto +0;" "exit;" ::: __clobber_all); } SEC("?raw_tp") __naked void bpf_jmp_r10(void) { asm volatile ( "r3 = 0 ll;" "call __bpf_jmp_r10;" "r0 = 0;" "exit;" ::: __clobber_all); } The following is the verifier failure log: 0: (18) r3 = 0x0 ; R3_w=0 2: (85) call pc+2 caller: R10=fp0 callee: frame1: R1=ctx() R3_w=0 R10=fp0 5: frame1: R1=ctx() R3_w=0 R10=fp0 ; asm volatile (" \ @ verifier_precision.c:184 5: (18) r2 = 0x20202000256c6c78 ; frame1: R2_w=0x20202000256c6c78 7: (05) goto pc+0 8: (bd) if r2 <= r10 goto pc+3 ; frame1: R2_w=0x20202000256c6c78 R10=fp0 9: (35) if r1 >= 0xffe3fff8 goto pc+0 ; frame1: R1=ctx() 10: (b5) if r2 <= 0x8 goto pc+0 mark_precise: frame1: last_idx 10 first_idx 0 subseq_idx -1 mark_precise: frame1: regs=r2 stack= before 9: (35) if r1 >= 0xffe3fff8 goto pc+0 mark_precise: frame1: regs=r2 stack= before 8: (bd) if r2 <= r10 goto pc+3 mark_preci ---truncated---

3.3 (Low)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
CWE-824 - Access of Uninitialized Pointer
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Low
CVE-2025-38345

In the Linux kernel, the following vulnerability has been resolved: ACPICA: fix acpi operand cache leak in dswstate.c ACPICA commit 987a3b5cf7175916e2a4b6ea5b8e70f830dfe732 I found an ACPI cache leak in ACPI early termination and boot continuing case. When early termination occurs due to malicious ACPI table, Linux kernel terminates ACPI function and continues to boot process. While kernel terminates ACPI function, kmem_cache_destroy() reports Acpi-Operand cache leak. Boot log of ACPI operand cache leak is as follows: >[ 0.585957] ACPI: Added _OSI(Module Device) >[ 0.587218] ACPI: Added _OSI(Processor Device) >[ 0.588530] ACPI: Added _OSI(3.0 _SCP Extensions) >[ 0.589790] ACPI: Added _OSI(Processor Aggregator Device) >[ 0.591534] ACPI Error: Illegal I/O port address/length above 64K: C806E00000004002/0x2 (20170303/hwvalid-155) >[ 0.594351] ACPI Exception: AE_LIMIT, Unable to initialize fixed events (20170303/evevent-88) >[ 0.597858] ACPI: Unable to start the ACPI Interpreter >[ 0.599162] ACPI Error: Could not remove SCI handler (20170303/evmisc-281) >[ 0.601836] kmem_cache_destroy Acpi-Operand: Slab cache still has objects >[ 0.603556] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.12.0-rc5 #26 >[ 0.605159] Hardware name: innotek gmb_h virtual_box/virtual_box, BIOS virtual_box 12/01/2006 >[ 0.609177] Call Trace: >[ 0.610063] ? dump_stack+0x5c/0x81 >[ 0.611118] ? kmem_cache_destroy+0x1aa/0x1c0 >[ 0.612632] ? acpi_sleep_proc_init+0x27/0x27 >[ 0.613906] ? acpi_os_delete_cache+0xa/0x10 >[ 0.617986] ? acpi_ut_delete_caches+0x3f/0x7b >[ 0.619293] ? acpi_terminate+0xa/0x14 >[ 0.620394] ? acpi_init+0x2af/0x34f >[ 0.621616] ? __class_create+0x4c/0x80 >[ 0.623412] ? video_setup+0x7f/0x7f >[ 0.624585] ? acpi_sleep_proc_init+0x27/0x27 >[ 0.625861] ? do_one_initcall+0x4e/0x1a0 >[ 0.627513] ? kernel_init_freeable+0x19e/0x21f >[ 0.628972] ? rest_init+0x80/0x80 >[ 0.630043] ? kernel_init+0xa/0x100 >[ 0.631084] ? ret_from_fork+0x25/0x30 >[ 0.633343] vgaarb: loaded >[ 0.635036] EDAC MC: Ver: 3.0.0 >[ 0.638601] PCI: Probing PCI hardware >[ 0.639833] PCI host bridge to bus 0000:00 >[ 0.641031] pci_bus 0000:00: root bus resource [io 0x0000-0xffff] > ... Continue to boot and log is omitted ... I analyzed this memory leak in detail and found acpi_ds_obj_stack_pop_and_ delete() function miscalculated the top of the stack. acpi_ds_obj_stack_push() function uses walk_state->operand_index for start position of the top, but acpi_ds_obj_stack_pop_and_delete() function considers index 0 for it. Therefore, this causes acpi operand memory leak. This cache leak causes a security threat because an old kernel (<= 4.9) shows memory locations of kernel functions in stack dump. Some malicious users could use this information to neutralize kernel ASLR. I made a patch to fix ACPI operand cache leak.

3.3 (Low)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
CWE-772 - Missing Release of Resource after Effective Lifetime
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Low
CVE-2025-38346

A flaw was found in the Linux kernel's Function Tracer (ftrace) subsystem. When an internal error disables function tracing and a kernel module is subsequently removed, the kernel fails to properly release tracking references associated with the unloaded module. A local user querying the kernel symbol table can trigger a use-after-free condition by accessing this deallocated memory, leading to a system crash and causing a Denial of Service (DoS).

5.5 (Medium)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE-416 - Use After Free
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Moderate
CVE-2025-38405

In the Linux kernel, the following vulnerability has been resolved: nvmet: fix memory leak of bio integrity If nvmet receives commands with metadata there is a continuous memory leak of kmalloc-128 slab or more precisely bio->bi_integrity. Since commit bf4c89fc8797 ("block: don't call bio_uninit from bio_endio") each user of bio_init has to use bio_uninit as well. Otherwise the bio integrity is not getting free. Nvmet uses bio_init for inline bios. Uninit the inline bio to complete deallocation of integrity in bio.

3.3 (Low)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
CWE-772 - Missing Release of Resource after Effective Lifetime
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Low
CVE-2025-38441

In the Linux kernel, the following vulnerability has been resolved: netfilter: flowtable: account for Ethernet header in nf_flow_pppoe_proto() syzbot found a potential access to uninit-value in nf_flow_pppoe_proto() Blamed commit forgot the Ethernet header. BUG: KMSAN: uninit-value in nf_flow_offload_inet_hook+0x7e4/0x940 net/netfilter/nf_flow_table_inet.c:27 nf_flow_offload_inet_hook+0x7e4/0x940 net/netfilter/nf_flow_table_inet.c:27 nf_hook_entry_hookfn include/linux/netfilter.h:157 [inline] nf_hook_slow+0xe1/0x3d0 net/netfilter/core.c:623 nf_hook_ingress include/linux/netfilter_netdev.h:34 [inline] nf_ingress net/core/dev.c:5742 [inline] __netif_receive_skb_core+0x4aff/0x70c0 net/core/dev.c:5837 __netif_receive_skb_one_core net/core/dev.c:5975 [inline] __netif_receive_skb+0xcc/0xac0 net/core/dev.c:6090 netif_receive_skb_internal net/core/dev.c:6176 [inline] netif_receive_skb+0x57/0x630 net/core/dev.c:6235 tun_rx_batched+0x1df/0x980 drivers/net/tun.c:1485 tun_get_user+0x4ee0/0x6b40 drivers/net/tun.c:1938 tun_chr_write_iter+0x3e9/0x5c0 drivers/net/tun.c:1984 new_sync_write fs/read_write.c:593 [inline] vfs_write+0xb4b/0x1580 fs/read_write.c:686 ksys_write fs/read_write.c:738 [inline] __do_sys_write fs/read_write.c:749 [inline]

5.5 (Medium)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE-908 - Use of Uninitialized Resource
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Moderate
CVE-2025-38470

A flaw was found in the Linux kernel's VLAN (Virtual Local Area Network) implementation. This vulnerability allows an authorized local user with network administration privileges to cause a Denial of Service (DoS) through a kernel crash or system memory exhaustion. The issue stems from a reference counting imbalance when dynamically toggling receiver VLAN filtering on active network interfaces.

5.5 (Medium)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE-911 - Improper Update of Reference Count
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Moderate
CVE-2025-39797

A flaw was found in the Linux kernel's XFRM subsystem, which handles Internet Protocol Security (IPsec) traffic. When assigning a Security Parameter Index (SPI)—a unique identifier used to manage encrypted network tunnels—the kernel fails to ensure that the identifier is globally unique across different inbound connections. An attacker negotiating IPsec connections can exploit this behavior to cause lookup conflicts for incoming traffic, leading to dropped network packets and a denial of service (DoS).

5.3 (Medium)
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
CWE-703 - Improper Check or Handling of Exceptional Conditions
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Moderate
CVE-2025-39866

A flaw was found in the Linux kernel. A race condition in the writeback subsystem can lead to a use-after-free vulnerability when an inode's writeback structure is concurrently switched. A local attacker with administrative privileges could trigger this flaw during writeback management operations to crash the kernel, resulting in a denial of service (DoS) or potentially allowing arbitrary code execution in the kernel context.

4.7 (Medium)
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE-416 - Use After Free
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Moderate
CVE-2025-40034

A flaw was found in the Linux kernel PCI/AER (Advanced Error Reporting) subsystem. When platform firmware reports error information via the ACPI APEI GHES mechanism for a device that does not advertise an AER capability, dev->aer_info remains NULL. The function aer_ratelimit() does not check for this condition, leading to a NULL pointer dereference.

6.6 (Medium)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H
CWE-476 - NULL Pointer Dereference
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Moderate
CVE-2025-40134

In the Linux kernel, the following vulnerability has been resolved: dm: fix NULL pointer dereference in __dm_suspend() There is a race condition between dm device suspend and table load that can lead to null pointer dereference. The issue occurs when suspend is invoked before table load completes: BUG: kernel NULL pointer dereference, address: 0000000000000054 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 6 PID: 6798 Comm: dmsetup Not tainted 6.6.0-g7e52f5f0ca9b #62 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 04/01/2014 RIP: 0010:blk_mq_wait_quiesce_done+0x0/0x50 Call Trace: <TASK> blk_mq_quiesce_queue+0x2c/0x50 dm_stop_queue+0xd/0x20 __dm_suspend+0x130/0x330 dm_suspend+0x11a/0x180 dev_suspend+0x27e/0x560 ctl_ioctl+0x4cf/0x850 dm_ctl_ioctl+0xd/0x20 vfs_ioctl+0x1d/0x50 __se_sys_ioctl+0x9b/0xc0 __x64_sys_ioctl+0x19/0x30 x64_sys_call+0x2c4a/0x4620 do_syscall_64+0x9e/0x1b0 The issue can be triggered as below: T1 T2 dm_suspend table_load __dm_suspend dm_setup_md_queue dm_mq_init_request_queue blk_mq_init_allocated_queue => q->mq_ops = set->ops; (1) dm_stop_queue / dm_wait_for_completion => q->tag_set NULL pointer! (2) => q->tag_set = set; (3) Fix this by checking if a valid table (map) exists before performing request-based suspend and waiting for target I/O. When map is NULL, skip these table-dependent suspend steps. Even when map is NULL, no I/O can reach any target because there is no table loaded; I/O submitted in this state will fail early in the DM layer. Skipping the table-dependent suspend logic in this case is safe and avoids NULL pointer dereferences.

4.7 (Medium)
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE-476 - NULL Pointer Dereference
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Moderate
CVE-2025-40210

A flaw was found in the Linux kernel's Network File System daemon (NFSD). A remote attacker can exploit this issue by sending a crafted NFSv4 COMPOUND request with an excessively large operation count, causing unbounded memory allocation. This failure can crash the kernel, resulting in a Denial of Service (DoS).

7.5 (High)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CWE-770 - Allocation of Resources Without Limits or Throttling
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Moderate
CVE-2025-40257

A flaw was found in the Linux kernel's Multipath TCP (MPTCP) implementation. A race condition in the `mptcp_pm_del_add_timer()` function allows for a use-after-free vulnerability. This can be exploited by a local attacker to cause a denial of service (DoS), potentially leading to privilege escalation or arbitrary code execution.

6.7 (Medium)
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
CWE-366 - Race Condition within a Thread
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Moderate
CVE-2025-40320

A flaw was found in the Linux kernel's Server Message Block (SMB) client component. When an active SMB network session retries a compound query, the kernel fails to reset an internal directory pointer that was already freed during the initial attempt. A local user with access to the mounted share, or an attacker capable of inducing connection retries, can trigger this use-after-free condition to cause kernel memory corruption or a Denial of Service (DoS) through a system crash.

6.3 (Medium)
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:H/A:H
CWE-825 - Expired Pointer Dereference
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Moderate
CVE-2025-71117

A flaw was found in the Linux kernel. A local user could exploit a vulnerability where freezing the request queue within certain sysfs store callbacks can lead to a deadlock. This issue may occur when combined with the device-mapper multipath (dm-multipath) driver and the `queue_if_no_path` option, or when sysfs attributes are set synchronously. Successful exploitation could result in a Denial of Service (DoS) by making the system unresponsive.

4.4 (Medium)
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
CWE-833 - Deadlock
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Low
CVE-2026-23002

In the Linux kernel, the following vulnerability has been resolved: lib/buildid: use __kernel_read() for sleepable context Prevent a "BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio". For the sleepable context, convert freader to use __kernel_read() instead of direct page cache access via read_cache_folio(). This simplifies the faultable code path by using the standard kernel file reading interface which handles all the complexity of reading file data. At the moment we are not changing the code for non-sleepable context which uses filemap_get_folio() and only succeeds if the target folios are already in memory and up-to-date. The reason is to keep the patch simple and easier to backport to stable kernels. Syzbot repro does not crash the kernel anymore and the selftests run successfully. In the follow up we will make __kernel_read() with IOCB_NOWAIT work for non-sleepable contexts. In addition, I would like to replace the secretmem check with a more generic approach and will add fstest for the buildid code.

4.7 (Medium)
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE-476 - NULL Pointer Dereference
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Low
CVE-2026-23040

A flaw was found in the Linux kernel's mac80211_hwsim virtual Wi-Fi driver. An incorrect frequency value used during Neighbor Awareness Networking (NAN) discovery notifications causes the driver to reference an invalid wireless channel, resulting in a null pointer dereference. A local attacker with privileges to configure wireless interfaces can trigger this flaw during network simulation, causing the kernel to crash and leading to a denial of service (DoS).

7.6 (High)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H
CWE-476 - NULL Pointer Dereference
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Moderate
CVE-2026-23111

A flaw was found in the Linux kernel's nf_tables component. A logic bug in nft_map_catchall_activate causes an inverted element activity check during the abort path of a failed transaction. This can lead to a use-after-free vulnerability, as catchall verdict elements may still reference a freed chain. A local low privileged user can exploit this to cause a denial of service or potentially achieve privilege escalation.

7.8 (High)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE-672 - Operation on a Resource after Expiration or Release
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Important
CVE-2026-23210

A flaw was found in the Linux kernel's ice network driver. A local attacker could exploit a race condition during the Virtual Station Interface (VSI) rebuild process. This flaw occurs when the Precision Time Protocol (PTP) periodic work attempts to access uninitialized memory, leading to a NULL pointer dereference. Successful exploitation results in a system crash, causing a Denial of Service (DoS).

7.0 (High)
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE-476 - NULL Pointer Dereference
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Moderate
CVE-2026-23243

A flaw was found in the Linux kernel's Remote Direct Memory Access (RDMA) `umad` (User Mode Access Device) component. A local user can exploit this vulnerability by manipulating input, causing an integer underflow that leads to an out-of-bounds memory write. This memory corruption can result in a denial of service (DoS) by crashing the system, and may also lead to limited information disclosure or data integrity issues.

7.3 (High)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H
CWE-131 - Incorrect Calculation of Buffer Size
Affected products
Fixed 309 products, the same list as for CVE-2024-56633
Threats
Impact Moderate
References
URL Category
https://access.redhat.com/errata/RHSA-2026:18134 self
https://docs.redhat.com/en/documentation/red_hat_… external
https://access.redhat.com/security/updates/classi… external
https://bugzilla.redhat.com/show_bug.cgi?id=2334549 external
https://bugzilla.redhat.com/show_bug.cgi?id=2350585 external
https://bugzilla.redhat.com/show_bug.cgi?id=2367614 external
https://bugzilla.redhat.com/show_bug.cgi?id=2373343 external
https://bugzilla.redhat.com/show_bug.cgi?id=2376060 external
https://bugzilla.redhat.com/show_bug.cgi?id=2376065 external
https://bugzilla.redhat.com/show_bug.cgi?id=2376382 external
https://bugzilla.redhat.com/show_bug.cgi?id=2379178 external
https://bugzilla.redhat.com/show_bug.cgi?id=2379187 external
https://bugzilla.redhat.com/show_bug.cgi?id=2379199 external
https://bugzilla.redhat.com/show_bug.cgi?id=2379237 external
https://bugzilla.redhat.com/show_bug.cgi?id=2379239 external
https://bugzilla.redhat.com/show_bug.cgi?id=2383399 external
https://bugzilla.redhat.com/show_bug.cgi?id=2383478 external
https://bugzilla.redhat.com/show_bug.cgi?id=2383906 external
https://bugzilla.redhat.com/show_bug.cgi?id=2396940 external
https://bugzilla.redhat.com/show_bug.cgi?id=2406782 external
https://bugzilla.redhat.com/show_bug.cgi?id=2414468 external
https://bugzilla.redhat.com/show_bug.cgi?id=2416307 external
https://bugzilla.redhat.com/show_bug.cgi?id=2418880 external
https://bugzilla.redhat.com/show_bug.cgi?id=2419945 external
https://bugzilla.redhat.com/show_bug.cgi?id=2436806 external
https://bugzilla.redhat.com/show_bug.cgi?id=2439687 external
https://bugzilla.redhat.com/show_bug.cgi?id=2439895 external
https://bugzilla.redhat.com/show_bug.cgi?id=2448594 external
https://issues.redhat.com/browse/RHEL-101339 external
https://issues.redhat.com/browse/RHEL-101343 external
https://issues.redhat.com/browse/RHEL-105431 external
https://issues.redhat.com/browse/RHEL-106452 external
https://issues.redhat.com/browse/RHEL-107274 external
https://issues.redhat.com/browse/RHEL-107916 external
https://issues.redhat.com/browse/RHEL-108683 external
https://issues.redhat.com/browse/RHEL-114532 external
https://issues.redhat.com/browse/RHEL-114533 external
https://issues.redhat.com/browse/RHEL-116076 external
https://issues.redhat.com/browse/RHEL-116876 external
https://issues.redhat.com/browse/RHEL-116879 external
https://issues.redhat.com/browse/RHEL-118599 external
https://issues.redhat.com/browse/RHEL-120364 external
https://issues.redhat.com/browse/RHEL-126233 external
https://issues.redhat.com/browse/RHEL-134732 external
https://issues.redhat.com/browse/RHEL-135143 external
https://issues.redhat.com/browse/RHEL-145936 external
https://issues.redhat.com/browse/RHEL-42486 external
https://security.access.redhat.com/data/csaf/v2/a… self
https://access.redhat.com/security/cve/CVE-2024-56633 self
https://bugzilla.redhat.com/show_bug.cgi?id=2334549 external
https://www.cve.org/CVERecord?id=CVE-2024-56633 external
https://nvd.nist.gov/vuln/detail/CVE-2024-56633 external
https://lore.kernel.org/linux-cve-announce/202412… external
https://access.redhat.com/security/cve/CVE-2025-21839 self
https://bugzilla.redhat.com/show_bug.cgi?id=2350585 external
https://www.cve.org/CVERecord?id=CVE-2025-21839 external
https://nvd.nist.gov/vuln/detail/CVE-2025-21839 external
https://lore.kernel.org/linux-cve-announce/202503… external
https://access.redhat.com/security/cve/CVE-2025-30156 self
https://bugzilla.redhat.com/show_bug.cgi?id=2393864 external
https://www.cve.org/CVERecord?id=CVE-2025-30156 external
https://nvd.nist.gov/vuln/detail/CVE-2025-30156 external
https://access.redhat.com/security/cve/CVE-2025-37980 self
https://bugzilla.redhat.com/show_bug.cgi?id=2367614 external
https://www.cve.org/CVERecord?id=CVE-2025-37980 external
https://nvd.nist.gov/vuln/detail/CVE-2025-37980 external
https://lore.kernel.org/linux-cve-announce/202505… external
https://access.redhat.com/security/cve/CVE-2025-38015 self
https://bugzilla.redhat.com/show_bug.cgi?id=2373343 external
https://www.cve.org/CVERecord?id=CVE-2025-38015 external
https://nvd.nist.gov/vuln/detail/CVE-2025-38015 external
https://lore.kernel.org/linux-cve-announce/202506… external
https://access.redhat.com/security/cve/CVE-2025-38097 self
https://bugzilla.redhat.com/show_bug.cgi?id=2376060 external
https://www.cve.org/CVERecord?id=CVE-2025-38097 external
https://nvd.nist.gov/vuln/detail/CVE-2025-38097 external
https://lore.kernel.org/linux-cve-announce/202507… external
https://access.redhat.com/security/cve/CVE-2025-38166 self
https://bugzilla.redhat.com/show_bug.cgi?id=2376065 external
https://www.cve.org/CVERecord?id=CVE-2025-38166 external
https://nvd.nist.gov/vuln/detail/CVE-2025-38166 external
https://lore.kernel.org/linux-cve-announce/202507… external
https://access.redhat.com/security/cve/CVE-2025-38202 self
https://bugzilla.redhat.com/show_bug.cgi?id=2376382 external
https://www.cve.org/CVERecord?id=CVE-2025-38202 external
https://nvd.nist.gov/vuln/detail/CVE-2025-38202 external
https://lore.kernel.org/linux-cve-announce/202507… external
https://access.redhat.com/security/cve/CVE-2025-38267 self
https://bugzilla.redhat.com/show_bug.cgi?id=2379187 external
https://www.cve.org/CVERecord?id=CVE-2025-38267 external
https://nvd.nist.gov/vuln/detail/CVE-2025-38267 external
https://lore.kernel.org/linux-cve-announce/202507… external
https://access.redhat.com/security/cve/CVE-2025-38275 self
https://bugzilla.redhat.com/show_bug.cgi?id=2379199 external
https://www.cve.org/CVERecord?id=CVE-2025-38275 external
https://nvd.nist.gov/vuln/detail/CVE-2025-38275 external
https://lore.kernel.org/linux-cve-announce/202507… external
https://access.redhat.com/security/cve/CVE-2025-38279 self
https://bugzilla.redhat.com/show_bug.cgi?id=2379178 external
https://www.cve.org/CVERecord?id=CVE-2025-38279 external
https://nvd.nist.gov/vuln/detail/CVE-2025-38279 external
https://lore.kernel.org/linux-cve-announce/202507… external
https://access.redhat.com/security/cve/CVE-2025-38345 self
https://bugzilla.redhat.com/show_bug.cgi?id=2379239 external
https://www.cve.org/CVERecord?id=CVE-2025-38345 external
https://nvd.nist.gov/vuln/detail/CVE-2025-38345 external
https://lore.kernel.org/linux-cve-announce/202507… external
https://access.redhat.com/security/cve/CVE-2025-38346 self
https://bugzilla.redhat.com/show_bug.cgi?id=2379237 external
https://www.cve.org/CVERecord?id=CVE-2025-38346 external
https://nvd.nist.gov/vuln/detail/CVE-2025-38346 external
https://lore.kernel.org/linux-cve-announce/202507… external
https://access.redhat.com/security/cve/CVE-2025-38405 self
https://bugzilla.redhat.com/show_bug.cgi?id=2383399 external
https://www.cve.org/CVERecord?id=CVE-2025-38405 external
https://nvd.nist.gov/vuln/detail/CVE-2025-38405 external
https://lore.kernel.org/linux-cve-announce/202507… external
https://access.redhat.com/security/cve/CVE-2025-38441 self
https://bugzilla.redhat.com/show_bug.cgi?id=2383478 external
https://www.cve.org/CVERecord?id=CVE-2025-38441 external
https://nvd.nist.gov/vuln/detail/CVE-2025-38441 external
https://lore.kernel.org/linux-cve-announce/202507… external
https://access.redhat.com/security/cve/CVE-2025-38470 self
https://bugzilla.redhat.com/show_bug.cgi?id=2383906 external
https://www.cve.org/CVERecord?id=CVE-2025-38470 external
https://nvd.nist.gov/vuln/detail/CVE-2025-38470 external
https://lore.kernel.org/linux-cve-announce/202507… external
https://access.redhat.com/security/cve/CVE-2025-39797 self
https://bugzilla.redhat.com/show_bug.cgi?id=2400057 external
https://www.cve.org/CVERecord?id=CVE-2025-39797 external
https://nvd.nist.gov/vuln/detail/CVE-2025-39797 external
https://lore.kernel.org/linux-cve-announce/202509… external
https://access.redhat.com/security/cve/CVE-2025-39866 self
https://bugzilla.redhat.com/show_bug.cgi?id=2396940 external
https://www.cve.org/CVERecord?id=CVE-2025-39866 external
https://nvd.nist.gov/vuln/detail/CVE-2025-39866 external
https://kernelcve.org/list/?q=CVE-2025-39866 external
https://lore.kernel.org/linux-cve-announce/202509… external
https://access.redhat.com/security/cve/CVE-2025-40034 self
https://bugzilla.redhat.com/show_bug.cgi?id=2406782 external
https://www.cve.org/CVERecord?id=CVE-2025-40034 external
https://nvd.nist.gov/vuln/detail/CVE-2025-40034 external
https://lore.kernel.org/linux-cve-announce/202510… external
https://access.redhat.com/security/cve/CVE-2025-40134 self
https://bugzilla.redhat.com/show_bug.cgi?id=2414468 external
https://www.cve.org/CVERecord?id=CVE-2025-40134 external
https://nvd.nist.gov/vuln/detail/CVE-2025-40134 external
https://lore.kernel.org/linux-cve-announce/202511… external
https://access.redhat.com/security/cve/CVE-2025-40210 self
https://bugzilla.redhat.com/show_bug.cgi?id=2416307 external
https://www.cve.org/CVERecord?id=CVE-2025-40210 external
https://nvd.nist.gov/vuln/detail/CVE-2025-40210 external
https://lore.kernel.org/linux-cve-announce/202511… external
https://access.redhat.com/security/cve/CVE-2025-40257 self
https://bugzilla.redhat.com/show_bug.cgi?id=2418880 external
https://www.cve.org/CVERecord?id=CVE-2025-40257 external
https://nvd.nist.gov/vuln/detail/CVE-2025-40257 external
https://lore.kernel.org/linux-cve-announce/202512… external
https://access.redhat.com/security/cve/CVE-2025-40320 self
https://bugzilla.redhat.com/show_bug.cgi?id=2419945 external
https://www.cve.org/CVERecord?id=CVE-2025-40320 external
https://nvd.nist.gov/vuln/detail/CVE-2025-40320 external
https://lore.kernel.org/linux-cve-announce/202512… external
https://access.redhat.com/security/cve/CVE-2025-71117 self
https://bugzilla.redhat.com/show_bug.cgi?id=2429589 external
https://www.cve.org/CVERecord?id=CVE-2025-71117 external
https://nvd.nist.gov/vuln/detail/CVE-2025-71117 external
https://lore.kernel.org/linux-cve-announce/202601… external
https://access.redhat.com/security/cve/CVE-2026-23002 self
https://bugzilla.redhat.com/show_bug.cgi?id=2432666 external
https://www.cve.org/CVERecord?id=CVE-2026-23002 external
https://nvd.nist.gov/vuln/detail/CVE-2026-23002 external
https://lore.kernel.org/linux-cve-announce/202601… external
https://access.redhat.com/security/cve/CVE-2026-23040 self
https://bugzilla.redhat.com/show_bug.cgi?id=2436806 external
https://www.cve.org/CVERecord?id=CVE-2026-23040 external
https://nvd.nist.gov/vuln/detail/CVE-2026-23040 external
https://lore.kernel.org/linux-cve-announce/202602… external
https://access.redhat.com/security/cve/CVE-2026-23111 self
https://bugzilla.redhat.com/show_bug.cgi?id=2439687 external
https://www.cve.org/CVERecord?id=CVE-2026-23111 external
https://nvd.nist.gov/vuln/detail/CVE-2026-23111 external
https://lore.kernel.org/linux-cve-announce/202602… external
https://access.redhat.com/security/cve/CVE-2026-23210 self
https://bugzilla.redhat.com/show_bug.cgi?id=2439895 external
https://www.cve.org/CVERecord?id=CVE-2026-23210 external
https://nvd.nist.gov/vuln/detail/CVE-2026-23210 external
https://lore.kernel.org/linux-cve-announce/202602… external
https://access.redhat.com/security/cve/CVE-2026-23243 self
https://bugzilla.redhat.com/show_bug.cgi?id=2448594 external
https://www.cve.org/CVERecord?id=CVE-2026-23243 external
https://nvd.nist.gov/vuln/detail/CVE-2026-23243 external
https://lore.kernel.org/linux-cve-announce/202603… external
To clipboard 

Loading 2.6 MB of JSON…



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    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.