Vulnerabilidades

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> staging: rtl8723bs: fix out-of-bounds read in rtw_get_ie() parser<br /> <br /> The Information Element (IE) parser rtw_get_ie() trusted the length<br /> byte of each IE without validating that the IE body (len bytes after<br /> the 2-byte header) fits inside the remaining frame buffer. A malformed<br /> frame can advertise an IE length larger than the available data, causing<br /> the parser to increment its pointer beyond the buffer end. This results<br /> in out-of-bounds reads or, depending on the pattern, an infinite loop.<br /> <br /> Fix by validating that (offset + 2 + len) does not exceed the limit<br /> before accepting the IE or advancing to the next element.<br /> <br /> This prevents OOB reads and ensures the parser terminates safely on<br /> malformed frames.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> binfmt_misc: restore write access before closing files opened by open_exec()<br /> <br /> bm_register_write() opens an executable file using open_exec(), which<br /> internally calls do_open_execat() and denies write access on the file to<br /> avoid modification while it is being executed.<br /> <br /> However, when an error occurs, bm_register_write() closes the file using<br /> filp_close() directly. This does not restore the write permission, which<br /> may cause subsequent write operations on the same file to fail.<br /> <br /> Fix this by calling exe_file_allow_write_access() before filp_close() to<br /> restore the write permission properly.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> nilfs2: avoid having an active sc_timer before freeing sci<br /> <br /> Because kthread_stop did not stop sc_task properly and returned -EINTR,<br /> the sc_timer was not properly closed, ultimately causing the problem [1]<br /> reported by syzbot when freeing sci due to the sc_timer not being closed.<br /> <br /> Because the thread sc_task main function nilfs_segctor_thread() returns 0<br /> when it succeeds, when the return value of kthread_stop() is not 0 in<br /> nilfs_segctor_destroy(), we believe that it has not properly closed<br /> sc_timer.<br /> <br /> We use timer_shutdown_sync() to sync wait for sc_timer to shutdown, and<br /> set the value of sc_task to NULL under the protection of lock<br /> sc_state_lock, so as to avoid the issue caused by sc_timer not being<br /> properly shutdowned.<br /> <br /> [1]<br /> ODEBUG: free active (active state 0) object: 00000000dacb411a object type: timer_list hint: nilfs_construction_timeout<br /> Call trace:<br /> nilfs_segctor_destroy fs/nilfs2/segment.c:2811 [inline]<br /> nilfs_detach_log_writer+0x668/0x8cc fs/nilfs2/segment.c:2877<br /> nilfs_put_super+0x4c/0x12c fs/nilfs2/super.c:509

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe<br /> <br /> The sit driver&amp;#39;s packet transmission path calls: sit_tunnel_xmit() -&gt;<br /> update_or_create_fnhe(), which lead to fnhe_remove_oldest() being called<br /> to delete entries exceeding FNHE_RECLAIM_DEPTH+random.<br /> <br /> The race window is between fnhe_remove_oldest() selecting fnheX for<br /> deletion and the subsequent kfree_rcu(). During this time, the<br /> concurrent path&amp;#39;s __mkroute_output() -&gt; find_exception() can fetch the<br /> soon-to-be-deleted fnheX, and rt_bind_exception() then binds it with a<br /> new dst using a dst_hold(). When the original fnheX is freed via RCU,<br /> the dst reference remains permanently leaked.<br /> <br /> CPU 0 CPU 1<br /> __mkroute_output()<br /> find_exception() [fnheX]<br /> update_or_create_fnhe()<br /> fnhe_remove_oldest() [fnheX]<br /> rt_bind_exception() [bind dst]<br /> RCU callback [fnheX freed, dst leak]<br /> <br /> This issue manifests as a device reference count leak and a warning in<br /> dmesg when unregistering the net device:<br /> <br /> unregister_netdevice: waiting for sitX to become free. Usage count = N<br /> <br /> Ido Schimmel provided the simple test validation method [1].<br /> <br /> The fix clears &amp;#39;oldest-&gt;fnhe_daddr&amp;#39; before calling fnhe_flush_routes().<br /> Since rt_bind_exception() checks this field, setting it to zero prevents<br /> the stale fnhe from being reused and bound to a new dst just before it<br /> is freed.<br /> <br /> [1]<br /> ip netns add ns1<br /> ip -n ns1 link set dev lo up<br /> ip -n ns1 address add 192.0.2.1/32 dev lo<br /> ip -n ns1 link add name dummy1 up type dummy<br /> ip -n ns1 route add 192.0.2.2/32 dev dummy1<br /> ip -n ns1 link add name gretap1 up arp off type gretap \<br /> local 192.0.2.1 remote 192.0.2.2<br /> ip -n ns1 route add 198.51.0.0/16 dev gretap1<br /> taskset -c 0 ip netns exec ns1 mausezahn gretap1 \<br /> -A 198.51.100.1 -B 198.51.0.0/16 -t udp -p 1000 -c 0 -q &amp;<br /> taskset -c 2 ip netns exec ns1 mausezahn gretap1 \<br /> -A 198.51.100.1 -B 198.51.0.0/16 -t udp -p 1000 -c 0 -q &amp;<br /> sleep 10<br /> ip netns pids ns1 | xargs kill<br /> ip netns del ns1

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> NFS: Fix LTP test failures when timestamps are delegated<br /> <br /> The utimes01 and utime06 tests fail when delegated timestamps are<br /> enabled, specifically in subtests that modify the atime and mtime<br /> fields using the &amp;#39;nobody&amp;#39; user ID.<br /> <br /> The problem can be reproduced as follow:<br /> <br /> # echo "/media *(rw,no_root_squash,sync)" &gt;&gt; /etc/exports<br /> # export -ra<br /> # mount -o rw,nfsvers=4.2 127.0.0.1:/media /tmpdir<br /> # cd /opt/ltp<br /> # ./runltp -d /tmpdir -s utimes01<br /> # ./runltp -d /tmpdir -s utime06<br /> <br /> This issue occurs because nfs_setattr does not verify the inode&amp;#39;s<br /> UID against the caller&amp;#39;s fsuid when delegated timestamps are<br /> permitted for the inode.<br /> <br /> This patch adds the UID check and if it does not match then the<br /> request is sent to the server for permission checking.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> NFS: Check the TLS certificate fields in nfs_match_client()<br /> <br /> If the TLS security policy is of type RPC_XPRTSEC_TLS_X509, then the<br /> cert_serial and privkey_serial fields need to match as well since they<br /> define the client&amp;#39;s identity, as presented to the server.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/i915: Avoid lock inversion when pinning to GGTT on CHV/BXT+VTD<br /> <br /> On completion of i915_vma_pin_ww(), a synchronous variant of<br /> dma_fence_work_commit() is called. When pinning a VMA to GGTT address<br /> space on a Cherry View family processor, or on a Broxton generation SoC<br /> with VTD enabled, i.e., when stop_machine() is then called from<br /> intel_ggtt_bind_vma(), that can potentially lead to lock inversion among<br /> reservation_ww and cpu_hotplug locks.<br /> <br /> [86.861179] ======================================================<br /> [86.861193] WARNING: possible circular locking dependency detected<br /> [86.861209] 6.15.0-rc5-CI_DRM_16515-gca0305cadc2d+ #1 Tainted: G U<br /> [86.861226] ------------------------------------------------------<br /> [86.861238] i915_module_loa/1432 is trying to acquire lock:<br /> [86.861252] ffffffff83489090 (cpu_hotplug_lock){++++}-{0:0}, at: stop_machine+0x1c/0x50<br /> [86.861290]<br /> but task is already holding lock:<br /> [86.861303] ffffc90002e0b4c8 (reservation_ww_class_mutex){+.+.}-{3:3}, at: i915_vma_pin.constprop.0+0x39/0x1d0 [i915]<br /> [86.862233]<br /> which lock already depends on the new lock.<br /> [86.862251]<br /> the existing dependency chain (in reverse order) is:<br /> [86.862265]<br /> -&gt; #5 (reservation_ww_class_mutex){+.+.}-{3:3}:<br /> [86.862292] dma_resv_lockdep+0x19a/0x390<br /> [86.862315] do_one_initcall+0x60/0x3f0<br /> [86.862334] kernel_init_freeable+0x3cd/0x680<br /> [86.862353] kernel_init+0x1b/0x200<br /> [86.862369] ret_from_fork+0x47/0x70<br /> [86.862383] ret_from_fork_asm+0x1a/0x30<br /> [86.862399]<br /> -&gt; #4 (reservation_ww_class_acquire){+.+.}-{0:0}:<br /> [86.862425] dma_resv_lockdep+0x178/0x390<br /> [86.862440] do_one_initcall+0x60/0x3f0<br /> [86.862454] kernel_init_freeable+0x3cd/0x680<br /> [86.862470] kernel_init+0x1b/0x200<br /> [86.862482] ret_from_fork+0x47/0x70<br /> [86.862495] ret_from_fork_asm+0x1a/0x30<br /> [86.862509]<br /> -&gt; #3 (&amp;mm-&gt;mmap_lock){++++}-{3:3}:<br /> [86.862531] down_read_killable+0x46/0x1e0<br /> [86.862546] lock_mm_and_find_vma+0xa2/0x280<br /> [86.862561] do_user_addr_fault+0x266/0x8e0<br /> [86.862578] exc_page_fault+0x8a/0x2f0<br /> [86.862593] asm_exc_page_fault+0x27/0x30<br /> [86.862607] filldir64+0xeb/0x180<br /> [86.862620] kernfs_fop_readdir+0x118/0x480<br /> [86.862635] iterate_dir+0xcf/0x2b0<br /> [86.862648] __x64_sys_getdents64+0x84/0x140<br /> [86.862661] x64_sys_call+0x1058/0x2660<br /> [86.862675] do_syscall_64+0x91/0xe90<br /> [86.862689] entry_SYSCALL_64_after_hwframe+0x76/0x7e<br /> [86.862703]<br /> -&gt; #2 (&amp;root-&gt;kernfs_rwsem){++++}-{3:3}:<br /> [86.862725] down_write+0x3e/0xf0<br /> [86.862738] kernfs_add_one+0x30/0x3c0<br /> [86.862751] kernfs_create_dir_ns+0x53/0xb0<br /> [86.862765] internal_create_group+0x134/0x4c0<br /> [86.862779] sysfs_create_group+0x13/0x20<br /> [86.862792] topology_add_dev+0x1d/0x30<br /> [86.862806] cpuhp_invoke_callback+0x4b5/0x850<br /> [86.862822] cpuhp_issue_call+0xbf/0x1f0<br /> [86.862836] __cpuhp_setup_state_cpuslocked+0x111/0x320<br /> [86.862852] __cpuhp_setup_state+0xb0/0x220<br /> [86.862866] topology_sysfs_init+0x30/0x50<br /> [86.862879] do_one_initcall+0x60/0x3f0<br /> [86.862893] kernel_init_freeable+0x3cd/0x680<br /> [86.862908] kernel_init+0x1b/0x200<br /> [86.862921] ret_from_fork+0x47/0x70<br /> [86.862934] ret_from_fork_asm+0x1a/0x30<br /> [86.862947]<br /> -&gt; #1 (cpuhp_state_mutex){+.+.}-{3:3}:<br /> [86.862969] __mutex_lock+0xaa/0xed0<br /> [86.862982] mutex_lock_nested+0x1b/0x30<br /> [86.862995] __cpuhp_setup_state_cpuslocked+0x67/0x320<br /> [86.863012] __cpuhp_setup_state+0xb0/0x220<br /> [86.863026] page_alloc_init_cpuhp+0x2d/0x60<br /> [86.863041] mm_core_init+0x22/0x2d0<br /> [86.863054] start_kernel+0x576/0xbd0<br /> [86.863068] x86_64_start_reservations+0x18/0x30<br /> [86.863084] x86_64_start_kernel+0xbf/0x110<br /> [86.863098] common_startup_64+0x13e/0x141<br /> [86.863114]<br /> -&gt; #0 (cpu_hotplug_lock){++++}-{0:0}:<br /> [86.863135] __lock_acquire+0x16<br /> ---truncated---

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: netpoll: fix incorrect refcount handling causing incorrect cleanup<br /> <br /> commit efa95b01da18 ("netpoll: fix use after free") incorrectly<br /> ignored the refcount and prematurely set dev-&gt;npinfo to NULL during<br /> netpoll cleanup, leading to improper behavior and memory leaks.<br /> <br /> Scenario causing lack of proper cleanup:<br /> <br /> 1) A netpoll is associated with a NIC (e.g., eth0) and netdev-&gt;npinfo is<br /> allocated, and refcnt = 1<br /> - Keep in mind that npinfo is shared among all netpoll instances. In<br /> this case, there is just one.<br /> <br /> 2) Another netpoll is also associated with the same NIC and<br /> npinfo-&gt;refcnt += 1.<br /> - Now dev-&gt;npinfo-&gt;refcnt = 2;<br /> - There is just one npinfo associated to the netdev.<br /> <br /> 3) When the first netpolls goes to clean up:<br /> - The first cleanup succeeds and clears np-&gt;dev-&gt;npinfo, ignoring<br /> refcnt.<br /> - It basically calls `RCU_INIT_POINTER(np-&gt;dev-&gt;npinfo, NULL);`<br /> - Set dev-&gt;npinfo = NULL, without proper cleanup<br /> - No -&gt;ndo_netpoll_cleanup() is either called<br /> <br /> 4) Now the second target tries to clean up<br /> - The second cleanup fails because np-&gt;dev-&gt;npinfo is already NULL.<br /> * In this case, ops-&gt;ndo_netpoll_cleanup() was never called, and<br /> the skb pool is not cleaned as well (for the second netpoll<br /> instance)<br /> - This leaks npinfo and skbpool skbs, which is clearly reported by<br /> kmemleak.<br /> <br /> Revert commit efa95b01da18 ("netpoll: fix use after free") and adds<br /> clarifying comments emphasizing that npinfo cleanup should only happen<br /> once the refcount reaches zero, ensuring stable and correct netpoll<br /> behavior.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ksmbd: close accepted socket when per-IP limit rejects connection<br /> <br /> When the per-IP connection limit is exceeded in ksmbd_kthread_fn(),<br /> the code sets ret = -EAGAIN and continues the accept loop without<br /> closing the just-accepted socket. That leaks one socket per rejected<br /> attempt from a single IP and enables a trivial remote DoS.<br /> <br /> Release client_sk before continuing.<br /> <br /> This bug was found with ZeroPath.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> posix-timers: Plug potential memory leak in do_timer_create()<br /> <br /> When posix timer creation is set to allocate a given timer ID and the<br /> access to the user space value faults, the function terminates without<br /> freeing the already allocated posix timer structure.<br /> <br /> Move the allocation after the user space access to cure that.<br /> <br /> [ tglx: Massaged change log ]

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> io_uring/cmd_net: fix wrong argument types for skb_queue_splice()<br /> <br /> If timestamp retriving needs to be retried and the local list of<br /> SKB&amp;#39;s already has entries, then it&amp;#39;s spliced back into the socket<br /> queue. However, the arguments for the splice helper are transposed,<br /> causing exactly the wrong direction of splicing into the on-stack<br /> list. Fix that up.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> nouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot<br /> <br /> nvkm_falcon_fw::boot is allocated, but no one frees it. This causes a<br /> kmemleak warning.<br /> <br /> Make sure this data is deallocated.