CVSS: -EPSS: 0%CPEs: 5EXPL: 0CVE-2024-41027 – Fix userfaultfd_api to return EINVAL as expected
https://notcve.org/view.php?id=CVE-2024-41027
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: 6.1EPSS: 0%CPEs: 4EXPL: 0CVE-2024-41023 – sched/deadline: Fix task_struct reference leak
https://notcve.org/view.php?id=CVE-2024-41023
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 •
CVSS: -EPSS: 0%CPEs: 8EXPL: 0CVE-2024-41022 – drm/amdgpu: Fix signedness bug in sdma_v4_0_process_trap_irq()
https://notcve.org/view.php?id=CVE-2024-41022
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix signedness bug in sdma_v4_0_process_trap_irq() The "instance" variable needs to be signed for the error handling to work. • https://git.kernel.org/stable/c/5594971e02764aa1c8210ffb838cb4e7897716e8 https://git.kernel.org/stable/c/8112fa72b7f139052843ff484130d6f97e9f052f https://git.kernel.org/stable/c/ea906e9ac61e3152bef63597f2d9f4a812fc346a https://git.kernel.org/stable/c/011552f29f20842c9a7a21bffe1f6a2d6457ba46 https://git.kernel.org/stable/c/5b0a3dc3e87821acb80e841b464d335aff242691 https://git.kernel.org/stable/c/0964c84b93db7fbf74f357c1e20957850e092db3 https://git.kernel.org/stable/c/8b2faf1a4f3b6c748c0da36cda865a226534d520 https://git.kernel.org/stable/c/3dd9734878a9042f0358301d19a2b006a •
CVSS: -EPSS: 0%CPEs: 9EXPL: 0CVE-2024-41020 – filelock: Fix fcntl/close race recovery compat path
https://notcve.org/view.php?id=CVE-2024-41020
In the Linux kernel, the following vulnerability has been resolved: filelock: Fix fcntl/close race recovery compat path When I wrote commit 3cad1bc01041 ("filelock: Remove locks reliably when fcntl/close race is detected"), I missed that there are two copies of the code I was patching: The normal version, and the version for 64-bit offsets on 32-bit kernels. Thanks to Greg KH for stumbling over this while doing the stable backport... Apply exactly the same fix to the compat path for 32-bit kernels. An LSM can prevent the fcntl/close race cleanup path in fcntl_setlk() from working, leading to use-after-free read in lock_get_status() when reading /proc/locks. • https://git.kernel.org/stable/c/c293621bbf678a3d85e3ed721c3921c8a670610d https://git.kernel.org/stable/c/a561145f3ae973ebf3e0aee41624e92a6c5cb38d https://git.kernel.org/stable/c/4c43ad4ab41602201d34c66ac62130fe339d686f https://git.kernel.org/stable/c/911cc83e56a2de5a40758766c6a70d6998248860 https://git.kernel.org/stable/c/53e21cfa68a7d12de378b7116c75571f73e0dfa2 https://git.kernel.org/stable/c/f4d0775c6e2f1340ca0725f0337de149aaa989ca https://git.kernel.org/stable/c/73ae349534ebc377328e7d21891e589626c6e82c https://git.kernel.org/stable/c/5b0af8e4c70e4b884bb94ff5f0cd49ecf •
CVSS: -EPSS: 0%CPEs: 6EXPL: 0CVE-2024-41019 – fs/ntfs3: Validate ff offset
https://notcve.org/view.php?id=CVE-2024-41019
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Validate ff offset This adds sanity checks for ff offset. There is a check on rt->first_free at first, but walking through by ff without any check. If the second ff is a large offset. We may encounter an out-of-bound read. • https://git.kernel.org/stable/c/35652dfa8cc9a8a900ec0f1e0395781f94ffc5f0 https://git.kernel.org/stable/c/818a257428644b8873e79c44404d8fb6598d4440 https://git.kernel.org/stable/c/6ae7265a7b816879fd0203e83b5030d3720bbb7a https://git.kernel.org/stable/c/82c94e6a7bd116724738aa67eba6f5fedf3a3319 https://git.kernel.org/stable/c/617cf144c206f98978ec730b17159344fd147cb4 https://git.kernel.org/stable/c/50c47879650b4c97836a0086632b3a2e300b0f06 •