Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> tipc: check attribute length for bearer name<br /> <br /> syzbot reported uninit-value:<br /> =====================================================<br /> BUG: KMSAN: uninit-value in string_nocheck lib/vsprintf.c:644 [inline]<br /> BUG: KMSAN: uninit-value in string+0x4f9/0x6f0 lib/vsprintf.c:725<br /> string_nocheck lib/vsprintf.c:644 [inline]<br /> string+0x4f9/0x6f0 lib/vsprintf.c:725<br /> vsnprintf+0x2222/0x3650 lib/vsprintf.c:2806<br /> vprintk_store+0x537/0x2150 kernel/printk/printk.c:2158<br /> vprintk_emit+0x28b/0xab0 kernel/printk/printk.c:2256<br /> vprintk_default+0x86/0xa0 kernel/printk/printk.c:2283<br /> vprintk+0x15f/0x180 kernel/printk/printk_safe.c:50<br /> _printk+0x18d/0x1cf kernel/printk/printk.c:2293<br /> tipc_enable_bearer net/tipc/bearer.c:371 [inline]<br /> __tipc_nl_bearer_enable+0x2022/0x22a0 net/tipc/bearer.c:1033<br /> tipc_nl_bearer_enable+0x6c/0xb0 net/tipc/bearer.c:1042<br /> genl_family_rcv_msg_doit net/netlink/genetlink.c:731 [inline]<br /> <br /> - Do sanity check the attribute length for TIPC_NLA_BEARER_NAME.<br /> - Do not use &amp;#39;illegal name&amp;#39; in printing message.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> f2fs: fix to clear dirty inode in f2fs_evict_inode()<br /> <br /> As Yanming reported in bugzilla:<br /> <br /> https://bugzilla.kernel.org/show_bug.cgi?id=215904<br /> <br /> The kernel message is shown below:<br /> <br /> kernel BUG at fs/f2fs/inode.c:825!<br /> Call Trace:<br /> evict+0x282/0x4e0<br /> __dentry_kill+0x2b2/0x4d0<br /> shrink_dentry_list+0x17c/0x4f0<br /> shrink_dcache_parent+0x143/0x1e0<br /> do_one_tree+0x9/0x30<br /> shrink_dcache_for_umount+0x51/0x120<br /> generic_shutdown_super+0x5c/0x3a0<br /> kill_block_super+0x90/0xd0<br /> kill_f2fs_super+0x225/0x310<br /> deactivate_locked_super+0x78/0xc0<br /> cleanup_mnt+0x2b7/0x480<br /> task_work_run+0xc8/0x150<br /> exit_to_user_mode_prepare+0x14a/0x150<br /> syscall_exit_to_user_mode+0x1d/0x40<br /> do_syscall_64+0x48/0x90<br /> <br /> The root cause is: inode node and dnode node share the same nid,<br /> so during f2fs_evict_inode(), dnode node truncation will invalidate<br /> its NAT entry, so when truncating inode node, it fails due to<br /> invalid NAT entry, result in inode is still marked as dirty, fix<br /> this issue by clearing dirty for inode and setting SBI_NEED_FSCK<br /> flag in filesystem.<br /> <br /> output from dump.f2fs:<br /> [print_node_info: 354] Node ID [0xf:15] is inode<br /> i_nid[0] [0x f : 15]

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amdgpu: Off by one in dm_dmub_outbox1_low_irq()<br /> <br /> The &gt; ARRAY_SIZE() should be &gt;= ARRAY_SIZE() to prevent an out of bounds<br /> access.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ksmbd: fix reference count leak in smb_check_perm_dacl()<br /> <br /> The issue happens in a specific path in smb_check_perm_dacl(). When<br /> "id" and "uid" have the same value, the function simply jumps out of<br /> the loop without decrementing the reference count of the object<br /> "posix_acls", which is increased by get_acl() earlier. This may<br /> result in memory leaks.<br /> <br /> Fix it by decreasing the reference count of "posix_acls" before<br /> jumping to label "check_access_bits".

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: dsa: mv88e6xxx: Fix refcount leak in mv88e6xxx_mdios_register<br /> <br /> of_get_child_by_name() returns a node pointer with refcount<br /> incremented, we should use of_node_put() on it when done.<br /> <br /> mv88e6xxx_mdio_register() pass the device node to of_mdiobus_register().<br /> We don&amp;#39;t need the device node after it.<br /> <br /> Add missing of_node_put() to avoid refcount leak.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: ethernet: mtk_eth_soc: out of bounds read in mtk_hwlro_get_fdir_entry()<br /> <br /> The "fsp-&gt;location" variable comes from user via ethtool_get_rxnfc().<br /> Check that it is valid to prevent an out of bounds read.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> amt: fix possible memory leak in amt_rcv()<br /> <br /> If an amt receives packets and it finds socket.<br /> If it can&amp;#39;t find a socket, it should free a received skb.<br /> But it doesn&amp;#39;t.<br /> So, a memory leak would possibly occur.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> firmware: dmi-sysfs: Fix memory leak in dmi_sysfs_register_handle<br /> <br /> kobject_init_and_add() takes reference even when it fails.<br /> According to the doc of kobject_init_and_add()<br /> <br /> If this function returns an error, kobject_put() must be called to<br /> properly clean up the memory associated with the object.<br /> <br /> Fix this issue by calling kobject_put().

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> driver core: fix deadlock in __device_attach<br /> <br /> In __device_attach function, The lock holding logic is as follows:<br /> ...<br /> __device_attach<br /> device_lock(dev) // get lock dev<br /> async_schedule_dev(__device_attach_async_helper, dev); // func<br /> async_schedule_node<br /> async_schedule_node_domain(func)<br /> entry = kzalloc(sizeof(struct async_entry), GFP_ATOMIC);<br /> /* when fail or work limit, sync to execute func, but<br /> __device_attach_async_helper will get lock dev as<br /> well, which will lead to A-A deadlock. */<br /> if (!entry || atomic_read(&amp;entry_count) &gt; MAX_WORK) {<br /> func;<br /> else<br /> queue_work_node(node, system_unbound_wq, &amp;entry-&gt;work)<br /> device_unlock(dev)<br /> <br /> As shown above, when it is allowed to do async probes, because of<br /> out of memory or work limit, async work is not allowed, to do<br /> sync execute instead. it will lead to A-A deadlock because of<br /> __device_attach_async_helper getting lock dev.<br /> <br /> To fix the deadlock, move the async_schedule_dev outside device_lock,<br /> as we can see, in async_schedule_node_domain, the parameter of<br /> queue_work_node is system_unbound_wq, so it can accept concurrent<br /> operations. which will also not change the code logic, and will<br /> not lead to deadlock.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> tcp: tcp_rtx_synack() can be called from process context<br /> <br /> Laurent reported the enclosed report [1]<br /> <br /> This bug triggers with following coditions:<br /> <br /> 0) Kernel built with CONFIG_DEBUG_PREEMPT=y<br /> <br /> 1) A new passive FastOpen TCP socket is created.<br /> This FO socket waits for an ACK coming from client to be a complete<br /> ESTABLISHED one.<br /> 2) A socket operation on this socket goes through lock_sock()<br /> release_sock() dance.<br /> 3) While the socket is owned by the user in step 2),<br /> a retransmit of the SYN is received and stored in socket backlog.<br /> 4) At release_sock() time, the socket backlog is processed while<br /> in process context.<br /> 5) A SYNACK packet is cooked in response of the SYN retransmit.<br /> 6) -&gt; tcp_rtx_synack() is called in process context.<br /> <br /> Before blamed commit, tcp_rtx_synack() was always called from BH handler,<br /> from a timer handler.<br /> <br /> Fix this by using TCP_INC_STATS() &amp; NET_INC_STATS()<br /> which do not assume caller is in non preemptible context.<br /> <br /> [1]<br /> BUG: using __this_cpu_add() in preemptible [00000000] code: epollpep/2180<br /> caller is tcp_rtx_synack.part.0+0x36/0xc0<br /> CPU: 10 PID: 2180 Comm: epollpep Tainted: G OE 5.16.0-0.bpo.4-amd64 #1 Debian 5.16.12-1~bpo11+1<br /> Hardware name: Supermicro SYS-5039MC-H8TRF/X11SCD-F, BIOS 1.7 11/23/2021<br /> Call Trace:<br /> <br /> dump_stack_lvl+0x48/0x5e<br /> check_preemption_disabled+0xde/0xe0<br /> tcp_rtx_synack.part.0+0x36/0xc0<br /> tcp_rtx_synack+0x8d/0xa0<br /> ? kmem_cache_alloc+0x2e0/0x3e0<br /> ? apparmor_file_alloc_security+0x3b/0x1f0<br /> inet_rtx_syn_ack+0x16/0x30<br /> tcp_check_req+0x367/0x610<br /> tcp_rcv_state_process+0x91/0xf60<br /> ? get_nohz_timer_target+0x18/0x1a0<br /> ? lock_timer_base+0x61/0x80<br /> ? preempt_count_add+0x68/0xa0<br /> tcp_v4_do_rcv+0xbd/0x270<br /> __release_sock+0x6d/0xb0<br /> release_sock+0x2b/0x90<br /> sock_setsockopt+0x138/0x1140<br /> ? __sys_getsockname+0x7e/0xc0<br /> ? aa_sk_perm+0x3e/0x1a0<br /> __sys_setsockopt+0x198/0x1e0<br /> __x64_sys_setsockopt+0x21/0x30<br /> do_syscall_64+0x38/0xc0<br /> entry_SYSCALL_64_after_hwframe+0x44/0xae

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> watchdog: ts4800_wdt: Fix refcount leak in ts4800_wdt_probe<br /> <br /> of_parse_phandle() returns a node pointer with refcount<br /> incremented, we should use of_node_put() on it when done.<br /> Add missing of_node_put() in some error paths.

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.