Page 204 of 2686 results (0.010 seconds)

CVSS: -EPSS: 0%CPEs: 4EXPL: 0

In the Linux kernel, the following vulnerability has been resolved: platform/x86: toshiba_acpi: Fix array out-of-bounds access In order to use toshiba_dmi_quirks[] together with the standard DMI matching functions, it must be terminated by a empty entry. Since this entry is missing, an array out-of-bounds access occurs every time the quirk list is processed. Fix this by adding the terminating empty entry. • https://git.kernel.org/stable/c/3cb1f40dfdc3b9f5449076c96b4e2523139f5cd0 https://git.kernel.org/stable/c/e030aa6c972641cb069086a8c7a0f747653e472a https://git.kernel.org/stable/c/639868f1cb87b683cf830353bbee0c4078202313 https://git.kernel.org/stable/c/0d71da43d6b7916d36cf1953d793da80433c50bf https://git.kernel.org/stable/c/b6e02c6b0377d4339986e07aeb696c632cd392aa •

CVSS: -EPSS: 0%CPEs: 5EXPL: 0

In the Linux kernel, the following vulnerability has been resolved: Fix userfaultfd_api to return EINVAL as expected Currently if we request a feature that is not set in the Kernel config we fail silently and return all the available features. However, the man page indicates we should return an EINVAL. We need to fix this issue since we can end up with a Kernel warning should a program request the feature UFFD_FEATURE_WP_UNPOPULATED on a kernel with the config not set with this feature. [ 200.812896] WARNING: CPU: 91 PID: 13634 at mm/memory.c:1660 zap_pte_range+0x43d/0x660 [ 200.820738] Modules linked in: [ 200.869387] CPU: 91 PID: 13634 Comm: userfaultfd Kdump: loaded Not tainted 6.9.0-rc5+ #8 [ 200.877477] Hardware name: Dell Inc. PowerEdge R6525/0N7YGH, BIOS 2.7.3 03/30/2022 [ 200.885052] RIP: 0010:zap_pte_range+0x43d/0x660 • https://git.kernel.org/stable/c/e06f1e1dd4998ffc9da37f580703b55a93fc4de4 https://git.kernel.org/stable/c/519547760f16eae7803d2658d9524bc5ba7a20a7 https://git.kernel.org/stable/c/14875fd5f9bcf60ac5518c63bfb676ade44aa7c6 https://git.kernel.org/stable/c/cd94cac4069a763ab5206be2c64c9a8beae590ba https://git.kernel.org/stable/c/8111f902b7c95d75fc80c7e577f5045886c6b384 https://git.kernel.org/stable/c/1723f04caacb32cadc4e063725d836a0c4450694 •

CVSS: -EPSS: 0%CPEs: 3EXPL: 0

In the Linux kernel, the following vulnerability has been resolved: misc: fastrpc: Fix memory leak in audio daemon attach operation Audio PD daemon send the name as part of the init IOCTL call. This name needs to be copied to kernel for which memory is allocated. This memory is never freed which might result in memory leak. Free the memory when it is not needed. • https://git.kernel.org/stable/c/0871561055e666da421d779397efcc1e5e964cab https://git.kernel.org/stable/c/8b8b82dcf393ceaca8c88939338fd4c30b5b11b2 https://git.kernel.org/stable/c/dbf4c31c9b039fd9734da156036492a2a7f78f64 https://git.kernel.org/stable/c/ad0bd973a033003ca578c42a760d1dc77aeea15e •

CVSS: -EPSS: 0%CPEs: 5EXPL: 0

In the Linux kernel, the following vulnerability has been resolved: misc: fastrpc: Restrict untrusted app to attach to privileged PD Untrusted application with access to only non-secure fastrpc device node can attach to root_pd or static PDs if it can make the respective init request. This can cause problems as the untrusted application can send bad requests to root_pd or static PDs. Add changes to reject attach to privileged PDs if the request is being made using non-secure fastrpc device node. • https://git.kernel.org/stable/c/0871561055e666da421d779397efcc1e5e964cab https://git.kernel.org/stable/c/5e305b5986dc52122a9368a1461f0c13e1de3fd6 https://git.kernel.org/stable/c/ea13bd807f1cef1af375d999980a9b9794c789b6 https://git.kernel.org/stable/c/c69fd8afacebfdf2f8a1ee1ea7e0723786529874 https://git.kernel.org/stable/c/bab2f5e8fd5d2f759db26b78d9db57412888f187 https://git.kernel.org/stable/c/2eb973ee4770a26d9b5e292b58ad29822d321c7f •

CVSS: 6.1EPSS: 0%CPEs: 4EXPL: 0

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. • https://git.kernel.org/stable/c/feff2e65efd8d84cf831668e182b2ce73c604bbb https://git.kernel.org/stable/c/f0e1c1d8ff908a39dd42e723d08f104505dfa601 https://git.kernel.org/stable/c/184c8ab5342450c4ae6fc5d937f9bb06c620dcf1 https://git.kernel.org/stable/c/7a54d31face626f62de415ebe77b43f76c3ffaf4 https://git.kernel.org/stable/c/b58652db66c910c2245f5bee7deca41c12d707b9 https://access.redhat.com/security/cve/CVE-2024-41023 https://bugzilla.redhat.com/show_bug.cgi?id=2300381 • CWE-401: Missing Release of Memory after Effective Lifetime •