CVSS: 7.8EPSS: 0%CPEs: 3EXPL: 0CVE-2022-49785 – x86/sgx: Add overflow check in sgx_validate_offset_length()
https://notcve.org/view.php?id=CVE-2022-49785
01 May 2025 — In the Linux kernel, the following vulnerability has been resolved: x86/sgx: Add overflow check in sgx_validate_offset_length() sgx_validate_offset_length() function verifies "offset" and "length" arguments provided by userspace, but was missing an overflow check on their addition. Add it. In the Linux kernel, the following vulnerability has been resolved: x86/sgx: Add overflow check in sgx_validate_offset_length() sgx_validate_offset_length() function verifies "offset" and "length" arguments provided by us... • https://git.kernel.org/stable/c/c6d26d370767fa227fc44b98a8bdad112efdf563 •
CVSS: 7.1EPSS: 0%CPEs: 2EXPL: 0CVE-2022-49784 – perf/x86/amd/uncore: Fix memory leak for events array
https://notcve.org/view.php?id=CVE-2022-49784
01 May 2025 — In the Linux kernel, the following vulnerability has been resolved: perf/x86/amd/uncore: Fix memory leak for events array When a CPU comes online, the per-CPU NB and LLC uncore contexts are freed but not the events array within the context structure. This causes a memory leak as identified by the kmemleak detector. [...] unreferenced object 0xffff8c5944b8e320 (size 32): comm "swapper/0", pid 1, jiffies 4294670387 (age 151.072s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ • https://git.kernel.org/stable/c/39621c5808f5dda75d03dc4b2d4d2b13a5a1c34b •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2022-49783 – x86/fpu: Drop fpregs lock before inheriting FPU permissions
https://notcve.org/view.php?id=CVE-2022-49783
01 May 2025 — In the Linux kernel, the following vulnerability has been resolved: x86/fpu: Drop fpregs lock before inheriting FPU permissions Mike Galbraith reported the following against an old fork of preempt-rt but the same issue also applies to the current preempt-rt tree. BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:46 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: systemd preempt_count: 1, expected: 0 RCU nest depth: 0, expected: 0 Preemption disabled at: fpu_c... • https://git.kernel.org/stable/c/9e798e9aa14c45fb94e47b30bf6347b369ce9df7 •
CVSS: 6.6EPSS: 0%CPEs: 2EXPL: 0CVE-2022-49782 – perf: Improve missing SIGTRAP checking
https://notcve.org/view.php?id=CVE-2022-49782
01 May 2025 — In the Linux kernel, the following vulnerability has been resolved: perf: Improve missing SIGTRAP checking To catch missing SIGTRAP we employ a WARN in __perf_event_overflow(), which fires if pending_sigtrap was already set: returning to user space without consuming pending_sigtrap, and then having the event fire again would re-enter the kernel and trigger the WARN. This, however, seemed to miss the case where some events not associated with progress in the user space task can fire and the interrupt handler... • https://git.kernel.org/stable/c/ca7b0a10287e2733bdafb01ef0d4038536625fe3 •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2022-49781 – perf/x86/amd: Fix crash due to race between amd_pmu_enable_all, perf NMI and throttling
https://notcve.org/view.php?id=CVE-2022-49781
01 May 2025 — In the Linux kernel, the following vulnerability has been resolved: perf/x86/amd: Fix crash due to race between amd_pmu_enable_all, perf NMI and throttling amd_pmu_enable_all() does: if (!test_bit(idx, cpuc->active_mask)) continue; amd_pmu_enable_event(cpuc->events[idx]); A perf NMI of another event can come between these two steps. Perf NMI handler internally disables and enables _all_ events, including the one which nmi-intercepted amd_pmu_enable_all() was in process of enabling. If that unintentionally e... • https://git.kernel.org/stable/c/ada543459cab7f653dcacdaba4011a8bb19c627c •
CVSS: 5.5EPSS: 0%CPEs: 6EXPL: 0CVE-2022-49780 – scsi: target: tcm_loop: Fix possible name leak in tcm_loop_setup_hba_bus()
https://notcve.org/view.php?id=CVE-2022-49780
01 May 2025 — In the Linux kernel, the following vulnerability has been resolved: scsi: target: tcm_loop: Fix possible name leak in tcm_loop_setup_hba_bus() If device_register() fails in tcm_loop_setup_hba_bus(), the name allocated by dev_set_name() need be freed. As comment of device_register() says, it should use put_device() to give up the reference in the error path. So fix this by calling put_device(), then the name can be freed in kobject_cleanup(). The 'tl_hba' will be freed in tcm_loop_release_adapter(), so it do... • https://git.kernel.org/stable/c/3703b2c5d041a68095cdd22380c23ce27d449ad7 •
CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2022-49779 – kprobes: Skip clearing aggrprobe's post_handler in kprobe-on-ftrace case
https://notcve.org/view.php?id=CVE-2022-49779
01 May 2025 — In the Linux kernel, the following vulnerability has been resolved: kprobes: Skip clearing aggrprobe's post_handler in kprobe-on-ftrace case In __unregister_kprobe_top(), if the currently unregistered probe has post_handler but other child probes of the aggrprobe do not have post_handler, the post_handler of the aggrprobe is cleared. If this is a ftrace-based probe, there is a problem. In later calls to disarm_kprobe(), we will use kprobe_ftrace_ops because post_handler is NULL. But we're armed with kprobe_... • https://git.kernel.org/stable/c/0bc11ed5ab60c135aa764a62c02cd5ea68289de4 •
CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0CVE-2022-49778 – arm64/mm: fix incorrect file_map_count for non-leaf pmd/pud
https://notcve.org/view.php?id=CVE-2022-49778
01 May 2025 — In the Linux kernel, the following vulnerability has been resolved: arm64/mm: fix incorrect file_map_count for non-leaf pmd/pud The page table check trigger BUG_ON() unexpectedly when collapse hugepage: ------------[ cut here ]------------ kernel BUG at mm/page_table_check.c:82! Internal error: Oops - BUG: 00000000f2000800 [#1] SMP Dumping ftrace buffer: (ftrace buffer empty) Modules linked in: CPU: 6 PID: 68 Comm: khugepaged Not tainted 6.1.0-rc3+ #750 Hardware name: linux,dummy-virt (DT) pstate: 60000005 ... • https://git.kernel.org/stable/c/42b2547137f5c974bb1bfd657c869fe96b96d86f •
CVSS: 7.1EPSS: 0%CPEs: 6EXPL: 0CVE-2022-49777 – Input: i8042 - fix leaking of platform device on module removal
https://notcve.org/view.php?id=CVE-2022-49777
01 May 2025 — In the Linux kernel, the following vulnerability has been resolved: Input: i8042 - fix leaking of platform device on module removal Avoid resetting the module-wide i8042_platform_device pointer in i8042_probe() or i8042_remove(), so that the device can be properly destroyed by i8042_exit() on module unload. In the Linux kernel, the following vulnerability has been resolved: Input: i8042 - fix leaking of platform device on module removal Avoid resetting the module-wide i8042_platform_device pointer in i8042_... • https://git.kernel.org/stable/c/68fdb0499653a2519691e645fcb72944f6e1e220 •
CVSS: 9.4EPSS: 0%CPEs: 7EXPL: 0CVE-2022-49776 – macvlan: enforce a consistent minimal mtu
https://notcve.org/view.php?id=CVE-2022-49776
01 May 2025 — In the Linux kernel, the following vulnerability has been resolved: macvlan: enforce a consistent minimal mtu macvlan should enforce a minimal mtu of 68, even at link creation. This patch avoids the current behavior (which could lead to crashes in ipv6 stack if the link is brought up) $ ip link add macvlan1 link eno1 mtu 8 type macvlan # This should fail ! $ ip link sh dev macvlan1 5: macvlan1@eno1: