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

RHSA-2024_10262

Vulnerability from csaf_redhat - Published: 2024-11-26 00:55 - Updated: 2024-12-11 21:49
Summary
Red Hat Security Advisory: kernel security update
Severity
Moderate
Notes
Topic: An update for kernel is now available for Red Hat Enterprise Linux 8.8 Extended Update Support. 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: improper input validation may lead to privilege escalation (CVE-2021-4204) * kernel: local privileges escalation in kernel/bpf/verifier.c (CVE-2022-23222) * kernel: Linux ebpf logic vulnerability leads to critical memory read and write gaining root privileges (CVE-2022-0500) * kernel: x86/mm: Randomize per-cpu entry area (CVE-2023-0597) * kernel: mm/sparsemem: fix race in accessing memory_section->usage (CVE-2023-52489) * kernel: blk-mq: fix IO hang from sbitmap wakeup race (CVE-2024-26671) * kernel: mac802154: fix llsec key resources release in mac802154_llsec_key_del (CVE-2024-26961) * kernel: nvme-tcp: fix UAF when detecting digest errors (CVE-2022-48686) * kernel: vt: fix unicode buffer corruption when deleting characters (CVE-2024-35823) * kernel: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs (CVE-2021-47393) * kernel: userfaultfd: fix a race between writeprotect and exit_mmap() (CVE-2021-47461) * kernel: scsi: mpi3mr: Avoid memcpy field-spanning write WARNING (CVE-2024-36920) * kernel: mptcp: ensure snd_nxt is properly initialized on connect (CVE-2024-36889) * kernel: bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE (CVE-2024-38564) * kernel: genirq/cpuhotplug, x86/vector: Prevent vector leak during CPU offline (CVE-2024-31076) * kernel: drm/radeon: fix UBSAN warning in kv_dpm.c (CVE-2024-40988) * kernel: xprtrdma: fix pointer derefs in error cases of rpcrdma_ep_create (CVE-2022-48773) * kernel: bpf: Fix overrunning reservations in ringbuf (CVE-2024-41009) * kernel: xfs: add bounds checking to xlog_recover_process_data (CVE-2024-41014) * kernel: sched/deadline: Fix task_struct reference leak (CVE-2024-41023) * kernel: bpf: Fix crash due to out of bounds access into reg2btf_ids. (CVE-2022-48929) * kernel: mptcp: pm: Fix uaf in __timer_delete_sync (CVE-2024-46858) 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.

An out-of-bounds (OOB) memory access flaw was found in the Linux kernel's eBPF due to an Improper Input Validation. This flaw allows a local attacker with a special privilege to crash the system or leak internal information.

CWE-119 - Improper Restriction of Operations within the Bounds of a Memory Buffer
Affected products
Product Identifier Version Remediation
Unresolved product id: BaseOS-8.8.0.Z.EUS:bpftool-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:bpftool-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:bpftool-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:bpftool-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:bpftool-debuginfo-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:bpftool-debuginfo-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:bpftool-debuginfo-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:bpftool-debuginfo-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-0:4.18.0-477.81.1.el8_8.src
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-abi-stablelists-0:4.18.0-477.81.1.el8_8.noarch
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-core-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-core-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-core-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-core-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-cross-headers-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-cross-headers-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-cross-headers-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-cross-headers-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-core-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-core-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-core-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-core-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-debuginfo-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-debuginfo-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-debuginfo-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-debuginfo-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-devel-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-devel-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-devel-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-devel-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-modules-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-modules-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-modules-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-modules-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-modules-extra-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-modules-extra-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-modules-extra-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debug-modules-extra-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debuginfo-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debuginfo-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debuginfo-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debuginfo-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debuginfo-common-aarch64-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debuginfo-common-ppc64le-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debuginfo-common-s390x-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-debuginfo-common-x86_64-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-devel-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-devel-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-devel-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-devel-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-doc-0:4.18.0-477.81.1.el8_8.noarch
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-headers-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-headers-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-headers-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-headers-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-modules-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-modules-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-modules-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-modules-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-modules-extra-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-modules-extra-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-modules-extra-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-modules-extra-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-debuginfo-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-debuginfo-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-debuginfo-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-debuginfo-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-libs-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-libs-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-libs-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-libs-devel-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-libs-devel-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-tools-libs-devel-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-zfcpdump-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-zfcpdump-core-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-zfcpdump-debuginfo-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-zfcpdump-devel-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-zfcpdump-modules-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:kernel-zfcpdump-modules-extra-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:perf-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:perf-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:perf-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:perf-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:perf-debuginfo-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:perf-debuginfo-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:perf-debuginfo-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:perf-debuginfo-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:python3-perf-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:python3-perf-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:python3-perf-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:python3-perf-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:python3-perf-debuginfo-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:python3-perf-debuginfo-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:python3-perf-debuginfo-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: BaseOS-8.8.0.Z.EUS:python3-perf-debuginfo-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:bpftool-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:bpftool-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:bpftool-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:bpftool-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:bpftool-debuginfo-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:bpftool-debuginfo-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:bpftool-debuginfo-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:bpftool-debuginfo-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-0:4.18.0-477.81.1.el8_8.src
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-abi-stablelists-0:4.18.0-477.81.1.el8_8.noarch
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-core-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-core-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-core-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-core-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-cross-headers-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-cross-headers-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-cross-headers-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-cross-headers-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-core-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-core-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-core-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-core-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-debuginfo-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-debuginfo-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-debuginfo-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-debuginfo-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-devel-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-devel-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-devel-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-devel-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-modules-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-modules-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-modules-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-modules-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-modules-extra-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-modules-extra-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-modules-extra-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debug-modules-extra-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debuginfo-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debuginfo-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debuginfo-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debuginfo-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debuginfo-common-aarch64-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debuginfo-common-ppc64le-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debuginfo-common-s390x-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-debuginfo-common-x86_64-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-devel-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-devel-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-devel-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-devel-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-doc-0:4.18.0-477.81.1.el8_8.noarch
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-headers-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-headers-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-headers-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-headers-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-modules-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-modules-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-modules-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-modules-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-modules-extra-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-modules-extra-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-modules-extra-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-modules-extra-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-tools-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-tools-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-tools-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-tools-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-tools-debuginfo-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-tools-debuginfo-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-tools-debuginfo-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-tools-debuginfo-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-tools-libs-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-tools-libs-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-tools-libs-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-tools-libs-devel-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-tools-libs-devel-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-tools-libs-devel-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-zfcpdump-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-zfcpdump-core-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-zfcpdump-debuginfo-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-zfcpdump-devel-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-zfcpdump-modules-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:kernel-zfcpdump-modules-extra-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:perf-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:perf-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:perf-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:perf-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:perf-debuginfo-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:perf-debuginfo-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:perf-debuginfo-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:perf-debuginfo-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:python3-perf-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:python3-perf-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:python3-perf-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:python3-perf-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:python3-perf-debuginfo-0:4.18.0-477.81.1.el8_8.aarch64
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:python3-perf-debuginfo-0:4.18.0-477.81.1.el8_8.ppc64le
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:python3-perf-debuginfo-0:4.18.0-477.81.1.el8_8.s390x
Vendor Fix fix
Workaround
Unresolved product id: CRB-8.8.0.Z.EUS:python3-perf-debuginfo-0:4.18.0-477.81.1.el8_8.x86_64
Vendor Fix fix
Workaround
Threats
Impact Moderate

In the Linux kernel, the following vulnerability has been resolved: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs Fan speed minimum can be enforced from sysfs. For example, setting current fan speed to 20 is used to enforce fan speed to be at 100% speed, 19 - to be not below 90% speed, etcetera. This feature provides ability to limit fan speed according to some system wise considerations, like absence of some replaceable units or high system ambient temperature. Request for changing fan minimum speed is configuration request and can be set only through 'sysfs' write procedure. In this situation value of argument 'state' is above nominal fan speed maximum. Return non-zero code in this case to avoid thermal_cooling_device_stats_update() call, because in this case statistics update violates thermal statistics table range. The issues is observed in case kernel is configured with option CONFIG_THERMAL_STATISTICS. Here is the trace from KASAN: [ 159.506659] BUG: KASAN: slab-out-of-bounds in thermal_cooling_device_stats_update+0x7d/0xb0 [ 159.516016] Read of size 4 at addr ffff888116163840 by task hw-management.s/7444 [ 159.545625] Call Trace: [ 159.548366] dump_stack+0x92/0xc1 [ 159.552084] ? thermal_cooling_device_stats_update+0x7d/0xb0 [ 159.635869] thermal_zone_device_update+0x345/0x780 [ 159.688711] thermal_zone_device_set_mode+0x7d/0xc0 [ 159.694174] mlxsw_thermal_modules_init+0x48f/0x590 [mlxsw_core] [ 159.700972] ? mlxsw_thermal_set_cur_state+0x5a0/0x5a0 [mlxsw_core] [ 159.731827] mlxsw_thermal_init+0x763/0x880 [mlxsw_core] [ 160.070233] RIP: 0033:0x7fd995909970 [ 160.074239] Code: 73 01 c3 48 8b 0d 28 d5 2b 00 f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 83 3d 99 2d 2c 00 00 75 10 b8 01 00 00 00 0f 05 <48> 3d 01 f0 ff .. [ 160.095242] RSP: 002b:00007fff54f5d938 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [ 160.103722] RAX: ffffffffffffffda RBX: 0000000000000013 RCX: 00007fd995909970 [ 160.111710] RDX: 0000000000000013 RSI: 0000000001906008 RDI: 0000000000000001 [ 160.119699] RBP: 0000000001906008 R08: 00007fd995bc9760 R09: 00007fd996210700 [ 160.127687] R10: 0000000000000073 R11: 0000000000000246 R12: 0000000000000013 [ 160.135673] R13: 0000000000000001 R14: 00007fd995bc8600 R15: 0000000000000013 [ 160.143671] [ 160.145338] Allocated by task 2924: [ 160.149242] kasan_save_stack+0x19/0x40 [ 160.153541] __kasan_kmalloc+0x7f/0xa0 [ 160.157743] __kmalloc+0x1a2/0x2b0 [ 160.161552] thermal_cooling_device_setup_sysfs+0xf9/0x1a0 [ 160.167687] __thermal_cooling_device_register+0x1b5/0x500 [ 160.173833] devm_thermal_of_cooling_device_register+0x60/0xa0 [ 160.180356] mlxreg_fan_probe+0x474/0x5e0 [mlxreg_fan] [ 160.248140] [ 160.249807] The buggy address belongs to the object at ffff888116163400 [ 160.249807] which belongs to the cache kmalloc-1k of size 1024 [ 160.263814] The buggy address is located 64 bytes to the right of [ 160.263814] 1024-byte region [ffff888116163400, ffff888116163800) [ 160.277536] The buggy address belongs to the page: [ 160.282898] page:0000000012275840 refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff888116167000 pfn:0x116160 [ 160.294872] head:0000000012275840 order:3 compound_mapcount:0 compound_pincount:0 [ 160.303251] flags: 0x200000000010200(slab|head|node=0|zone=2) [ 160.309694] raw: 0200000000010200 ffffea00046f7208 ffffea0004928208 ffff88810004dbc0 [ 160.318367] raw: ffff888116167000 00000000000a0006 00000001ffffffff 0000000000000000 [ 160.327033] page dumped because: kasan: bad access detected [ 160.333270] [ 160.334937] Memory state around the buggy address: [ 160.356469] >ffff888116163800: fc ..

CWE-754 - Improper Check for Unusual or Exceptional Conditions
Affected products
Fixed 214 products, the same list as for CVE-2021-4204
Threats
Impact Moderate

A possible race condition flaw was found in the Linux kernel. When a process exits, its virtual memory areas (VMAs) are removed by exit_mmap(), and at the same time, userfaultfd_writeprotect() is called.

CWE-362 - Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Affected products
Fixed 214 products, the same list as for CVE-2021-4204
Threats
Impact Moderate

A flaw was found in unrestricted eBPF usage by the BPF_BTF_LOAD, leading to a possible out-of-bounds memory write in the Linux kernel’s BPF subsystem due to the way a user loads BTF. This flaw allows a local user to crash or escalate their privileges on the system.

CWE-787 - Out-of-bounds Write
Affected products
Fixed 214 products, the same list as for CVE-2021-4204
Threats
Impact Moderate

A flaw was found in the Linux kernel's adjust_ptr_min_max_vals in the kernel/bpf/verifier.c function. In this flaw, a missing sanity check for *_OR_NULL pointer types that perform pointer arithmetic may cause a kernel information leak issue.

CWE-763 - Release of Invalid Pointer or Reference
Affected products
Fixed 214 products, the same list as for CVE-2021-4204
Threats
Impact Moderate

A use-after-free vulnerability was found in the Linux kernel in drivers/nvme/host/tcp.c in nvme_tcp_io_work. This issue can occur when a local user continues to read data after the connection finishes. This flaw allows a malicious user to cause a use-after-free problem.

Affected products
Fixed 214 products, the same list as for CVE-2021-4204
Threats
Impact Moderate

In the Linux kernel, the following vulnerability has been resolved: xprtrdma: fix pointer derefs in error cases of rpcrdma_ep_create If there are failures then we must not leave the non-NULL pointers with the error value, otherwise `rpcrdma_ep_destroy` gets confused and tries free them, resulting in an Oops.

CWE-476 - NULL Pointer Dereference
Affected products
Fixed 214 products, the same list as for CVE-2021-4204
Threats
Impact Moderate

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix crash due to out of bounds access into reg2btf_ids. When commit e6ac2450d6de ("bpf: Support bpf program calling kernel function") added kfunc support, it defined reg2btf_ids as a cheap way to translate the verifier reg type to the appropriate btf_vmlinux BTF ID, however commit c25b2ae13603 ("bpf: Replace PTR_TO_XXX_OR_NULL with PTR_TO_XXX | PTR_MAYBE_NULL") moved the __BPF_REG_TYPE_MAX from the last member of bpf_reg_type enum to after the base register types, and defined other variants using type flag composition. However, now, the direct usage of reg->type to index into reg2btf_ids may no longer fall into __BPF_REG_TYPE_MAX range, and hence lead to out of bounds access and kernel crash on dereference of bad pointer.

CWE-125 - Out-of-bounds Read
Affected products
Fixed 214 products, the same list as for CVE-2021-4204
Threats
Impact Moderate

A possible unauthorized memory access flaw was found in the Linux kernel cpu_entry_area mapping of X86 CPU data to memory, where a user may guess the location of exception stack(s) or other important data. This issue could allow a local user to gain access to some important data with expected location in memory.

CWE-401 - Missing Release of Memory after Effective Lifetime
Affected products
Fixed 214 products, the same list as for CVE-2021-4204
Threats
Impact Moderate

A race condition was found on a PFN in the Linux Kernel, which can fall into the device memory region with the system memory configuration. Normal zone start and end PFNs contain the device memory PFNs as well, and the compaction triggered will try on the device memory PFNs and end up in NOP. This may lead to compromised Availability.

CWE-362 - Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Affected products
Fixed 214 products, the same list as for CVE-2021-4204
Threats
Impact Moderate

In the Linux kernel, the following vulnerability has been resolved: blk-mq: fix IO hang from sbitmap wakeup race In blk_mq_mark_tag_wait(), __add_wait_queue() may be re-ordered with the following blk_mq_get_driver_tag() in case of getting driver tag failure. Then in __sbitmap_queue_wake_up(), waitqueue_active() may not observe the added waiter in blk_mq_mark_tag_wait() and wake up nothing, meantime blk_mq_mark_tag_wait() can't get driver tag successfully. This issue can be reproduced by running the following test in loop, and fio hang can be observed in < 30min when running it on my test VM in laptop. modprobe -r scsi_debug modprobe scsi_debug delay=0 dev_size_mb=4096 max_queue=1 host_max_queue=1 submit_queues=4 dev=`ls -d /sys/bus/pseudo/drivers/scsi_debug/adapter*/host*/target*/*/block/* | head -1 | xargs basename` fio --filename=/dev/"$dev" --direct=1 --rw=randrw --bs=4k --iodepth=1 \ --runtime=100 --numjobs=40 --time_based --name=test \ --ioengine=libaio Fix the issue by adding one explicit barrier in blk_mq_mark_tag_wait(), which is just fine in case of running out of tag.

CWE-362 - Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Affected products
Fixed 214 products, the same list as for CVE-2021-4204
Threats
Impact Moderate

A flaw was found in the Linux Kernel where resources are improperly managed in IEEE 802.15.4 networking, leading to a potential use-after-free issue, resulting in a denial of service.

CWE-459 - Incomplete Cleanup
Affected products
Fixed 214 products, the same list as for CVE-2021-4204
Threats
Impact Moderate

In the Linux kernel, the following vulnerability has been resolved: genirq/cpuhotplug, x86/vector: Prevent vector leak during CPU offline The absence of IRQD_MOVE_PCNTXT prevents immediate effectiveness of interrupt affinity reconfiguration via procfs. Instead, the change is deferred until the next instance of the interrupt being triggered on the original CPU. When the interrupt next triggers on the original CPU, the new affinity is enforced within __irq_move_irq(). A vector is allocated from the new CPU, but the old vector on the original CPU remains and is not immediately reclaimed. Instead, apicd->move_in_progress is flagged, and the reclaiming process is delayed until the next trigger of the interrupt on the new CPU. Upon the subsequent triggering of the interrupt on the new CPU, irq_complete_move() adds a task to the old CPU's vector_cleanup list if it remains online. Subsequently, the timer on the old CPU iterates over its vector_cleanup list, reclaiming old vectors. However, a rare scenario arises if the old CPU is outgoing before the interrupt triggers again on the new CPU. In that case irq_force_complete_move() is not invoked on the outgoing CPU to reclaim the old apicd->prev_vector because the interrupt isn't currently affine to the outgoing CPU, and irq_needs_fixup() returns false. Even though __vector_schedule_cleanup() is later called on the new CPU, it doesn't reclaim apicd->prev_vector; instead, it simply resets both apicd->move_in_progress and apicd->prev_vector to 0. As a result, the vector remains unreclaimed in vector_matrix, leading to a CPU vector leak. To address this issue, move the invocation of irq_force_complete_move() before the irq_needs_fixup() call to reclaim apicd->prev_vector, if the interrupt is currently or used to be affine to the outgoing CPU. Additionally, reclaim the vector in __vector_schedule_cleanup() as well, following a warning message, although theoretically it should never see apicd->move_in_progress with apicd->prev_cpu pointing to an offline CPU.

CWE-402 - Transmission of Private Resources into a New Sphere ('Resource Leak')
Affected products
Fixed 214 products, the same list as for CVE-2021-4204
Threats
Impact Low

A vulnerability as found in the Linux kernel’s virtual terminal (VT) subsystem, which could lead to unicode buffer corruption when deleting characters. This issue arises from improper handling of unicode data, which can corrupt memory or lead to unintended behavior.

Affected products
Fixed 214 products, the same list as for CVE-2021-4204
Threats
Impact Moderate

In the Linux kernel, the following vulnerability has been resolved: mptcp: ensure snd_nxt is properly initialized on connect Christoph reported a splat hinting at a corrupted snd_una: WARNING: CPU: 1 PID: 38 at net/mptcp/protocol.c:1005 __mptcp_clean_una+0x4b3/0x620 net/mptcp/protocol.c:1005 Modules linked in: CPU: 1 PID: 38 Comm: kworker/1:1 Not tainted 6.9.0-rc1-gbbeac67456c9 #59 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.11.0-2.el7 04/01/2014 Workqueue: events mptcp_worker RIP: 0010:__mptcp_clean_una+0x4b3/0x620 net/mptcp/protocol.c:1005 Code: be 06 01 00 00 bf 06 01 00 00 e8 a8 12 e7 fe e9 00 fe ff ff e8 8e 1a e7 fe 0f b7 ab 3e 02 00 00 e9 d3 fd ff ff e8 7d 1a e7 fe <0f> 0b 4c 8b bb e0 05 00 00 e9 74 fc ff ff e8 6a 1a e7 fe 0f 0b e9 RSP: 0018:ffffc9000013fd48 EFLAGS: 00010293 RAX: 0000000000000000 RBX: ffff8881029bd280 RCX: ffffffff82382fe4 RDX: ffff8881003cbd00 RSI: ffffffff823833c3 RDI: 0000000000000001 RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000000 R11: fefefefefefefeff R12: ffff888138ba8000 R13: 0000000000000106 R14: ffff8881029bd908 R15: ffff888126560000 FS: 0000000000000000(0000) GS:ffff88813bd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f604a5dae38 CR3: 0000000101dac002 CR4: 0000000000170ef0 Call Trace: <TASK> __mptcp_clean_una_wakeup net/mptcp/protocol.c:1055 [inline] mptcp_clean_una_wakeup net/mptcp/protocol.c:1062 [inline] __mptcp_retrans+0x7f/0x7e0 net/mptcp/protocol.c:2615 mptcp_worker+0x434/0x740 net/mptcp/protocol.c:2767 process_one_work+0x1e0/0x560 kernel/workqueue.c:3254 process_scheduled_works kernel/workqueue.c:3335 [inline] worker_thread+0x3c7/0x640 kernel/workqueue.c:3416 kthread+0x121/0x170 kernel/kthread.c:388 ret_from_fork+0x44/0x50 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:243 </TASK> When fallback to TCP happens early on a client socket, snd_nxt is not yet initialized and any incoming ack will copy such value into snd_una. If the mptcp worker (dumbly) tries mptcp-level re-injection after such ack, that would unconditionally trigger a send buffer cleanup using 'bad' snd_una values. We could easily disable re-injection for fallback sockets, but such dumb behavior already helped catching a few subtle issues and a very low to zero impact in practice. Instead address the issue always initializing snd_nxt (and write_seq, for consistency) at connect time.

CWE-665 - Improper Initialization
Affected products
Fixed 214 products, the same list as for CVE-2021-4204
Threats
Impact Moderate

In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Avoid memcpy field-spanning write WARNING When the "storcli2 show" command is executed for eHBA-9600, mpi3mr driver prints this WARNING message: memcpy: detected field-spanning write (size 128) of single field "bsg_reply_buf->reply_buf" at drivers/scsi/mpi3mr/mpi3mr_app.c:1658 (size 1) WARNING: CPU: 0 PID: 12760 at drivers/scsi/mpi3mr/mpi3mr_app.c:1658 mpi3mr_bsg_request+0x6b12/0x7f10 [mpi3mr] The cause of the WARN is 128 bytes memcpy to the 1 byte size array "__u8 replay_buf[1]" in the struct mpi3mr_bsg_in_reply_buf. The array is intended to be a flexible length array, so the WARN is a false positive. To suppress the WARN, remove the constant number '1' from the array declaration and clarify that it has flexible length. Also, adjust the memory allocation size to match the change.

Affected products
Fixed 214 products, the same list as for CVE-2021-4204
Threats
Impact Low

In the Linux kernel, the following vulnerability has been resolved: bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE bpf_prog_attach uses attach_type_to_prog_type to enforce proper attach type for BPF_PROG_TYPE_CGROUP_SKB. link_create uses bpf_prog_get and relies on bpf_prog_attach_check_attach_type to properly verify prog_type <> attach_type association. Add missing attach_type enforcement for the link_create case. Otherwise, it's currently possible to attach cgroup_skb prog types to other cgroup hooks.

CWE-665 - Improper Initialization
Affected products
Fixed 214 products, the same list as for CVE-2021-4204
Threats
Impact Low

In the Linux kernel, the following vulnerability has been resolved: drm/radeon: fix UBSAN warning in kv_dpm.c Adds bounds check for sumo_vid_mapping_entry.

CWE-787 - Out-of-bounds Write
Affected products
Fixed 214 products, the same list as for CVE-2021-4204
Threats
Impact Moderate

An out-of-bounds memory access flaw was found in the Linux kernel’s BPF subsystem. This flaw allows a local user to crash the system.

CWE-121 - Stack-based Buffer Overflow
Affected products
Fixed 214 products, the same list as for CVE-2021-4204
Threats
Impact Moderate

In the Linux kernel, the following vulnerability has been resolved: xfs: add bounds checking to xlog_recover_process_data There is a lack of verification of the space occupied by fixed members of xlog_op_header in the xlog_recover_process_data. We can create a crafted image to trigger an out of bounds read by following these steps: 1) Mount an image of xfs, and do some file operations to leave records 2) Before umounting, copy the image for subsequent steps to simulate abnormal exit. Because umount will ensure that tail_blk and head_blk are the same, which will result in the inability to enter xlog_recover_process_data 3) Write a tool to parse and modify the copied image in step 2 4) Make the end of the xlog_op_header entries only 1 byte away from xlog_rec_header->h_size 5) xlog_rec_header->h_num_logops++ 6) Modify xlog_rec_header->h_crc Fix: Add a check to make sure there is sufficient space to access fixed members of xlog_op_header.

CWE-125 - Out-of-bounds Read
Affected products
Fixed 214 products, the same list as for CVE-2021-4204
Threats
Impact Moderate

In the Linux kernel, the following vulnerability has been resolved: sched/deadline: Fix task_struct reference leak During the execution of the following stress test with linux-rt: stress-ng --cyclic 30 --timeout 30 --minimize --quiet kmemleak frequently reported a memory leak concerning the task_struct: unreferenced object 0xffff8881305b8000 (size 16136): comm "stress-ng", pid 614, jiffies 4294883961 (age 286.412s) object hex dump (first 32 bytes): 02 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 .@.............. 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ debug hex dump (first 16 bytes): 53 09 00 00 00 00 00 00 00 00 00 00 00 00 00 00 S............... backtrace: [<00000000046b6790>] dup_task_struct+0x30/0x540 [<00000000c5ca0f0b>] copy_process+0x3d9/0x50e0 [<00000000ced59777>] kernel_clone+0xb0/0x770 [<00000000a50befdc>] __do_sys_clone+0xb6/0xf0 [<000000001dbf2008>] do_syscall_64+0x5d/0xf0 [<00000000552900ff>] entry_SYSCALL_64_after_hwframe+0x6e/0x76 The issue occurs in start_dl_timer(), which increments the task_struct reference count and sets a timer. The timer callback, dl_task_timer, is supposed to decrement the reference count upon expiration. However, if enqueue_task_dl() is called before the timer expires and cancels it, the reference count is not decremented, leading to the leak. This patch fixes the reference leak by ensuring the task_struct reference count is properly decremented when the timer is canceled.

CWE-401 - Missing Release of Memory after Effective Lifetime
Affected products
Fixed 214 products, the same list as for CVE-2021-4204
Threats
Impact Moderate

In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: Fix uaf in __timer_delete_sync There are two paths to access mptcp_pm_del_add_timer, result in a race condition: CPU1 CPU2 ==== ==== net_rx_action napi_poll netlink_sendmsg __napi_poll netlink_unicast process_backlog netlink_unicast_kernel __netif_receive_skb genl_rcv __netif_receive_skb_one_core netlink_rcv_skb NF_HOOK genl_rcv_msg ip_local_deliver_finish genl_family_rcv_msg ip_protocol_deliver_rcu genl_family_rcv_msg_doit tcp_v4_rcv mptcp_pm_nl_flush_addrs_doit tcp_v4_do_rcv mptcp_nl_remove_addrs_list tcp_rcv_established mptcp_pm_remove_addrs_and_subflows tcp_data_queue remove_anno_list_by_saddr mptcp_incoming_options mptcp_pm_del_add_timer mptcp_pm_del_add_timer kfree(entry) In remove_anno_list_by_saddr(running on CPU2), after leaving the critical zone protected by "pm.lock", the entry will be released, which leads to the occurrence of uaf in the mptcp_pm_del_add_timer(running on CPU1). Keeping a reference to add_timer inside the lock, and calling sk_stop_timer_sync() with this reference, instead of "entry->add_timer". Move list_del(&entry->list) to mptcp_pm_del_add_timer and inside the pm lock, do not directly access any members of the entry outside the pm lock, which can avoid similar "entry->x" uaf.

CWE-416 - Use After Free
Affected products
Fixed 214 products, the same list as for CVE-2021-4204
Threats
Impact Moderate
References
URL Category
https://access.redhat.com/errata/RHSA-2024:10262 self
https://access.redhat.com/security/updates/classi… external
https://bugzilla.redhat.com/show_bug.cgi?id=2039178 external
https://bugzilla.redhat.com/show_bug.cgi?id=2043520 external
https://bugzilla.redhat.com/show_bug.cgi?id=2044578 external
https://bugzilla.redhat.com/show_bug.cgi?id=2165926 external
https://bugzilla.redhat.com/show_bug.cgi?id=2269189 external
https://bugzilla.redhat.com/show_bug.cgi?id=2272811 external
https://bugzilla.redhat.com/show_bug.cgi?id=2278176 external
https://bugzilla.redhat.com/show_bug.cgi?id=2278931 external
https://bugzilla.redhat.com/show_bug.cgi?id=2281190 external
https://bugzilla.redhat.com/show_bug.cgi?id=2282345 external
https://bugzilla.redhat.com/show_bug.cgi?id=2282896 external
https://bugzilla.redhat.com/show_bug.cgi?id=2284515 external
https://bugzilla.redhat.com/show_bug.cgi?id=2284571 external
https://bugzilla.redhat.com/show_bug.cgi?id=2293429 external
https://bugzilla.redhat.com/show_bug.cgi?id=2293684 external
https://bugzilla.redhat.com/show_bug.cgi?id=2297572 external
https://bugzilla.redhat.com/show_bug.cgi?id=2298109 external
https://bugzilla.redhat.com/show_bug.cgi?id=2298412 external
https://bugzilla.redhat.com/show_bug.cgi?id=2300297 external
https://bugzilla.redhat.com/show_bug.cgi?id=2300381 external
https://bugzilla.redhat.com/show_bug.cgi?id=2315210 external
https://security.access.redhat.com/data/csaf/v2/a… self
https://access.redhat.com/security/cve/CVE-2021-4204 self
https://bugzilla.redhat.com/show_bug.cgi?id=2039178 external
https://www.cve.org/CVERecord?id=CVE-2021-4204 external
https://nvd.nist.gov/vuln/detail/CVE-2021-4204 external
https://www.openwall.com/lists/oss-security/2022/… external
https://access.redhat.com/security/cve/CVE-2021-47393 self
https://bugzilla.redhat.com/show_bug.cgi?id=2282345 external
https://www.cve.org/CVERecord?id=CVE-2021-47393 external
https://nvd.nist.gov/vuln/detail/CVE-2021-47393 external
https://lore.kernel.org/linux-cve-announce/202405… external
https://access.redhat.com/security/cve/CVE-2021-47461 self
https://bugzilla.redhat.com/show_bug.cgi?id=2282896 external
https://www.cve.org/CVERecord?id=CVE-2021-47461 external
https://nvd.nist.gov/vuln/detail/CVE-2021-47461 external
https://lore.kernel.org/linux-cve-announce/202405… external
https://access.redhat.com/security/cve/CVE-2022-0500 self
https://bugzilla.redhat.com/show_bug.cgi?id=2044578 external
https://www.cve.org/CVERecord?id=CVE-2022-0500 external
https://nvd.nist.gov/vuln/detail/CVE-2022-0500 external
https://git.kernel.org/pub/scm/linux/kernel/git/t… external
https://git.kernel.org/pub/scm/linux/kernel/git/t… external
https://git.kernel.org/pub/scm/linux/kernel/git/t… external
https://git.kernel.org/pub/scm/linux/kernel/git/t… external
https://git.kernel.org/pub/scm/linux/kernel/git/t… external
https://git.kernel.org/pub/scm/linux/kernel/git/t… external
https://git.kernel.org/pub/scm/linux/kernel/git/t… external
https://access.redhat.com/security/cve/CVE-2022-23222 self
https://bugzilla.redhat.com/show_bug.cgi?id=2043520 external
https://www.cve.org/CVERecord?id=CVE-2022-23222 external
https://nvd.nist.gov/vuln/detail/CVE-2022-23222 external
https://www.openwall.com/lists/oss-security/2022/… external
https://access.redhat.com/security/cve/CVE-2022-48686 self
https://bugzilla.redhat.com/show_bug.cgi?id=2278931 external
https://www.cve.org/CVERecord?id=CVE-2022-48686 external
https://nvd.nist.gov/vuln/detail/CVE-2022-48686 external
https://lore.kernel.org/linux-cve-announce/202405… external
https://access.redhat.com/security/cve/CVE-2022-48773 self
https://bugzilla.redhat.com/show_bug.cgi?id=2298109 external
https://www.cve.org/CVERecord?id=CVE-2022-48773 external
https://nvd.nist.gov/vuln/detail/CVE-2022-48773 external
https://lore.kernel.org/linux-cve-announce/202407… external
https://access.redhat.com/security/cve/CVE-2022-48929 self
https://bugzilla.redhat.com/show_bug.cgi?id=2307185 external
https://www.cve.org/CVERecord?id=CVE-2022-48929 external
https://nvd.nist.gov/vuln/detail/CVE-2022-48929 external
https://lore.kernel.org/linux-cve-announce/202408… external
https://access.redhat.com/security/cve/CVE-2023-0597 self
https://bugzilla.redhat.com/show_bug.cgi?id=2165926 external
https://www.cve.org/CVERecord?id=CVE-2023-0597 external
https://nvd.nist.gov/vuln/detail/CVE-2023-0597 external
https://lore.kernel.org/lkml/Yz%2FmfJ1gjgshF19t@h… external
https://access.redhat.com/security/cve/CVE-2023-52489 self
https://bugzilla.redhat.com/show_bug.cgi?id=2269189 external
https://www.cve.org/CVERecord?id=CVE-2023-52489 external
https://nvd.nist.gov/vuln/detail/CVE-2023-52489 external
https://lore.kernel.org/linux-cve-announce/202402… external
https://access.redhat.com/security/cve/CVE-2024-26671 self
https://bugzilla.redhat.com/show_bug.cgi?id=2272811 external
https://www.cve.org/CVERecord?id=CVE-2024-26671 external
https://nvd.nist.gov/vuln/detail/CVE-2024-26671 external
https://lore.kernel.org/linux-cve-announce/202404… external
https://access.redhat.com/security/cve/CVE-2024-26961 self
https://bugzilla.redhat.com/show_bug.cgi?id=2278176 external
https://www.cve.org/CVERecord?id=CVE-2024-26961 external
https://nvd.nist.gov/vuln/detail/CVE-2024-26961 external
https://lore.kernel.org/linux-cve-announce/202405… external
https://access.redhat.com/security/cve/CVE-2024-31076 self
https://bugzilla.redhat.com/show_bug.cgi?id=2293684 external
https://www.cve.org/CVERecord?id=CVE-2024-31076 external
https://nvd.nist.gov/vuln/detail/CVE-2024-31076 external
https://lore.kernel.org/linux-cve-announce/202406… external
https://access.redhat.com/security/cve/CVE-2024-35823 self
https://bugzilla.redhat.com/show_bug.cgi?id=2281190 external
https://www.cve.org/CVERecord?id=CVE-2024-35823 external
https://nvd.nist.gov/vuln/detail/CVE-2024-35823 external
https://lore.kernel.org/linux-cve-announce/202405… external
https://access.redhat.com/security/cve/CVE-2024-36889 self
https://bugzilla.redhat.com/show_bug.cgi?id=2284571 external
https://www.cve.org/CVERecord?id=CVE-2024-36889 external
https://nvd.nist.gov/vuln/detail/CVE-2024-36889 external
https://lore.kernel.org/linux-cve-announce/202405… external
https://access.redhat.com/security/cve/CVE-2024-36920 self
https://bugzilla.redhat.com/show_bug.cgi?id=2284515 external
https://www.cve.org/CVERecord?id=CVE-2024-36920 external
https://nvd.nist.gov/vuln/detail/CVE-2024-36920 external
https://lore.kernel.org/linux-cve-announce/202405… external
https://access.redhat.com/security/cve/CVE-2024-38564 self
https://bugzilla.redhat.com/show_bug.cgi?id=2293429 external
https://www.cve.org/CVERecord?id=CVE-2024-38564 external
https://nvd.nist.gov/vuln/detail/CVE-2024-38564 external
https://lore.kernel.org/linux-cve-announce/202406… external
https://access.redhat.com/security/cve/CVE-2024-40988 self
https://bugzilla.redhat.com/show_bug.cgi?id=2297572 external
https://www.cve.org/CVERecord?id=CVE-2024-40988 external
https://nvd.nist.gov/vuln/detail/CVE-2024-40988 external
https://lore.kernel.org/linux-cve-announce/202407… external
https://access.redhat.com/security/cve/CVE-2024-41009 self
https://bugzilla.redhat.com/show_bug.cgi?id=2298412 external
https://www.cve.org/CVERecord?id=CVE-2024-41009 external
https://nvd.nist.gov/vuln/detail/CVE-2024-41009 external
https://lore.kernel.org/linux-cve-announce/202407… external
https://access.redhat.com/security/cve/CVE-2024-41014 self
https://bugzilla.redhat.com/show_bug.cgi?id=2300297 external
https://www.cve.org/CVERecord?id=CVE-2024-41014 external
https://nvd.nist.gov/vuln/detail/CVE-2024-41014 external
https://lore.kernel.org/linux-cve-announce/202407… external
https://access.redhat.com/security/cve/CVE-2024-41023 self
https://bugzilla.redhat.com/show_bug.cgi?id=2300381 external
https://www.cve.org/CVERecord?id=CVE-2024-41023 external
https://nvd.nist.gov/vuln/detail/CVE-2024-41023 external
https://lore.kernel.org/linux-cve-announce/202407… external
https://access.redhat.com/security/cve/CVE-2024-46858 self
https://bugzilla.redhat.com/show_bug.cgi?id=2315210 external
https://www.cve.org/CVERecord?id=CVE-2024-46858 external
https://nvd.nist.gov/vuln/detail/CVE-2024-46858 external
https://lore.kernel.org/linux-cve-announce/202409… external

Loading 1.5 MB of JSON…



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…