Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> mtd: core: Fix refcount error in del_mtd_device()<br /> <br /> del_mtd_device() will call of_node_put() to mtd_get_of_node(mtd), which<br /> is mtd-&gt;dev.of_node. However, memset(&amp;mtd-&gt;dev, 0) is called before<br /> of_node_put(). As the result, of_node_put() won&amp;#39;t do anything in<br /> del_mtd_device(), and causes the refcount leak.<br /> <br /> del_mtd_device()<br /> memset(&amp;mtd-&gt;dev, 0, sizeof(mtd-&gt;dev) # clear mtd-&gt;dev<br /> of_node_put()<br /> mtd_get_of_node(mtd) # mtd-&gt;dev is cleared, can&amp;#39;t locate of_node<br /> # of_node_put(NULL) won&amp;#39;t do anything<br /> <br /> Fix the error by caching the pointer of the device_node.<br /> <br /> OF: ERROR: memory leak, expected refcount 1 instead of 2,<br /> of_node_get()/of_node_put() unbalanced - destroy cset entry: attach<br /> overlay node /spi/spi-sram@0<br /> CPU: 3 PID: 275 Comm: python3 Tainted: G N 6.1.0-rc3+ #54<br /> 0d8a1edddf51f172ff5226989a7565c6313b08e2<br /> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS<br /> rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014<br /> Call Trace:<br /> <br /> dump_stack_lvl+0x67/0x83<br /> kobject_get+0x155/0x160<br /> of_node_get+0x1f/0x30<br /> of_fwnode_get+0x43/0x70<br /> fwnode_handle_get+0x54/0x80<br /> fwnode_get_nth_parent+0xc9/0xe0<br /> fwnode_full_name_string+0x3f/0xa0<br /> device_node_string+0x30f/0x750<br /> pointer+0x598/0x7a0<br /> vsnprintf+0x62d/0x9b0<br /> ...<br /> cfs_overlay_release+0x30/0x90<br /> config_item_release+0xbe/0x1a0<br /> config_item_put+0x5e/0x80<br /> configfs_rmdir+0x3bd/0x540<br /> vfs_rmdir+0x18c/0x320<br /> do_rmdir+0x198/0x330<br /> __x64_sys_rmdir+0x2c/0x40<br /> do_syscall_64+0x37/0x90<br /> entry_SYSCALL_64_after_hwframe+0x63/0xcd<br /> <br /> [: Light reword of the commit log]

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

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ARC: mm: fix leakage of memory allocated for PTE<br /> <br /> Since commit d9820ff ("ARC: mm: switch pgtable_t back to struct page *")<br /> a memory leakage problem occurs. Memory allocated for page table entries<br /> not released during process termination. This issue can be reproduced by<br /> a small program that allocates a large amount of memory. After several<br /> runs, you&amp;#39;ll see that the amount of free memory has reduced and will<br /> continue to reduce after each run. All ARC CPUs are effected by this<br /> issue. The issue was introduced since the kernel stable release v5.15-rc1.<br /> <br /> As described in commit d9820ff after switch pgtable_t back to struct<br /> page *, a pointer to "struct page" and appropriate functions are used to<br /> allocate and free a memory page for PTEs, but the pmd_pgtable macro hasn&amp;#39;t<br /> changed and returns the direct virtual address from the PMD (PGD) entry.<br /> Than this address used as a parameter in the __pte_free() and as a result<br /> this function couldn&amp;#39;t release memory page allocated for PTEs.<br /> <br /> Fix this issue by changing the pmd_pgtable macro and returning pointer to<br /> struct page.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> Bluetooth: hci_conn: Fix crash on hci_create_cis_sync<br /> <br /> When attempting to connect multiple ISO sockets without using<br /> DEFER_SETUP may result in the following crash:<br /> <br /> BUG: KASAN: null-ptr-deref in hci_create_cis_sync+0x18b/0x2b0<br /> Read of size 2 at addr 0000000000000036 by task kworker/u3:1/50<br /> <br /> CPU: 0 PID: 50 Comm: kworker/u3:1 Not tainted<br /> 6.0.0-rc7-02243-gb84a13ff4eda #4373<br /> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009),<br /> BIOS 1.16.0-1.fc36 04/01/2014<br /> Workqueue: hci0 hci_cmd_sync_work<br /> Call Trace:<br /> <br /> dump_stack_lvl+0x19/0x27<br /> kasan_report+0xbc/0xf0<br /> ? hci_create_cis_sync+0x18b/0x2b0<br /> hci_create_cis_sync+0x18b/0x2b0<br /> ? get_link_mode+0xd0/0xd0<br /> ? __ww_mutex_lock_slowpath+0x10/0x10<br /> ? mutex_lock+0xe0/0xe0<br /> ? get_link_mode+0xd0/0xd0<br /> hci_cmd_sync_work+0x111/0x190<br /> process_one_work+0x427/0x650<br /> worker_thread+0x87/0x750<br /> ? process_one_work+0x650/0x650<br /> kthread+0x14e/0x180<br /> ? kthread_exit+0x50/0x50<br /> ret_from_fork+0x22/0x30<br />

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> mm/uffd: fix warning without PTE_MARKER_UFFD_WP compiled in<br /> <br /> When PTE_MARKER_UFFD_WP not configured, it&amp;#39;s still possible to reach pte<br /> marker code and trigger an warning. Add a few CONFIG_PTE_MARKER_UFFD_WP<br /> ifdefs to make sure the code won&amp;#39;t be reached when not compiled in.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> clk: samsung: Fix memory leak in _samsung_clk_register_pll()<br /> <br /> If clk_register() fails, @pll-&gt;rate_table may have allocated memory by<br /> kmemdup(), so it needs to be freed, otherwise will cause memory leak<br /> issue, this patch fixes it.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> clk: tegra20: Fix refcount leak in tegra20_clock_init<br /> <br /> of_find_matching_node() returns a node pointer with refcount<br /> incremented, we should use of_node_put() on it when not need anymore.<br /> Add missing of_node_put() to avoid refcount leak.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> xfrm: Reinject transport-mode packets through workqueue<br /> <br /> The following warning is displayed when the tcp6-multi-diffip11 stress<br /> test case of the LTP test suite is tested:<br /> <br /> watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [ns-tcpserver:48198]<br /> CPU: 0 PID: 48198 Comm: ns-tcpserver Kdump: loaded Not tainted 6.0.0-rc6+ #39<br /> Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015<br /> pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)<br /> pc : des3_ede_encrypt+0x27c/0x460 [libdes]<br /> lr : 0x3f<br /> sp : ffff80000ceaa1b0<br /> x29: ffff80000ceaa1b0 x28: ffff0000df056100 x27: ffff0000e51e5280<br /> x26: ffff80004df75030 x25: ffff0000e51e4600 x24: 000000000000003b<br /> x23: 0000000000802080 x22: 000000000000003d x21: 0000000000000038<br /> x20: 0000000080000020 x19: 000000000000000a x18: 0000000000000033<br /> x17: ffff0000e51e4780 x16: ffff80004e2d1448 x15: ffff80004e2d1248<br /> x14: ffff0000e51e4680 x13: ffff80004e2d1348 x12: ffff80004e2d1548<br /> x11: ffff80004e2d1848 x10: ffff80004e2d1648 x9 : ffff80004e2d1748<br /> x8 : ffff80004e2d1948 x7 : 000000000bcaf83d x6 : 000000000000001b<br /> x5 : ffff80004e2d1048 x4 : 00000000761bf3bf x3 : 000000007f1dd0a3<br /> x2 : ffff0000e51e4780 x1 : ffff0000e3b9a2f8 x0 : 00000000db44e872<br /> Call trace:<br /> des3_ede_encrypt+0x27c/0x460 [libdes]<br /> crypto_des3_ede_encrypt+0x1c/0x30 [des_generic]<br /> crypto_cbc_encrypt+0x148/0x190<br /> crypto_skcipher_encrypt+0x2c/0x40<br /> crypto_authenc_encrypt+0xc8/0xfc [authenc]<br /> crypto_aead_encrypt+0x2c/0x40<br /> echainiv_encrypt+0x144/0x1a0 [echainiv]<br /> crypto_aead_encrypt+0x2c/0x40<br /> esp6_output_tail+0x1c8/0x5d0 [esp6]<br /> esp6_output+0x120/0x278 [esp6]<br /> xfrm_output_one+0x458/0x4ec<br /> xfrm_output_resume+0x6c/0x1f0<br /> xfrm_output+0xac/0x4ac<br /> __xfrm6_output+0x130/0x270<br /> xfrm6_output+0x60/0xec<br /> ip6_xmit+0x2ec/0x5bc<br /> inet6_csk_xmit+0xbc/0x10c<br /> __tcp_transmit_skb+0x460/0x8c0<br /> tcp_write_xmit+0x348/0x890<br /> __tcp_push_pending_frames+0x44/0x110<br /> tcp_rcv_established+0x3c8/0x720<br /> tcp_v6_do_rcv+0xdc/0x4a0<br /> tcp_v6_rcv+0xc24/0xcb0<br /> ip6_protocol_deliver_rcu+0xf0/0x574<br /> ip6_input_finish+0x48/0x7c<br /> ip6_input+0x48/0xc0<br /> ip6_rcv_finish+0x80/0x9c<br /> xfrm_trans_reinject+0xb0/0xf4<br /> tasklet_action_common.constprop.0+0xf8/0x134<br /> tasklet_action+0x30/0x3c<br /> __do_softirq+0x128/0x368<br /> do_softirq+0xb4/0xc0<br /> __local_bh_enable_ip+0xb0/0xb4<br /> put_cpu_fpsimd_context+0x40/0x70<br /> kernel_neon_end+0x20/0x40<br /> sha1_base_do_update.constprop.0.isra.0+0x11c/0x140 [sha1_ce]<br /> sha1_ce_finup+0x94/0x110 [sha1_ce]<br /> crypto_shash_finup+0x34/0xc0<br /> hmac_finup+0x48/0xe0<br /> crypto_shash_finup+0x34/0xc0<br /> shash_digest_unaligned+0x74/0x90<br /> crypto_shash_digest+0x4c/0x9c<br /> shash_ahash_digest+0xc8/0xf0<br /> shash_async_digest+0x28/0x34<br /> crypto_ahash_digest+0x48/0xcc<br /> crypto_authenc_genicv+0x88/0xcc [authenc]<br /> crypto_authenc_encrypt+0xd8/0xfc [authenc]<br /> crypto_aead_encrypt+0x2c/0x40<br /> echainiv_encrypt+0x144/0x1a0 [echainiv]<br /> crypto_aead_encrypt+0x2c/0x40<br /> esp6_output_tail+0x1c8/0x5d0 [esp6]<br /> esp6_output+0x120/0x278 [esp6]<br /> xfrm_output_one+0x458/0x4ec<br /> xfrm_output_resume+0x6c/0x1f0<br /> xfrm_output+0xac/0x4ac<br /> __xfrm6_output+0x130/0x270<br /> xfrm6_output+0x60/0xec<br /> ip6_xmit+0x2ec/0x5bc<br /> inet6_csk_xmit+0xbc/0x10c<br /> __tcp_transmit_skb+0x460/0x8c0<br /> tcp_write_xmit+0x348/0x890<br /> __tcp_push_pending_frames+0x44/0x110<br /> tcp_push+0xb4/0x14c<br /> tcp_sendmsg_locked+0x71c/0xb64<br /> tcp_sendmsg+0x40/0x6c<br /> inet6_sendmsg+0x4c/0x80<br /> sock_sendmsg+0x5c/0x6c<br /> __sys_sendto+0x128/0x15c<br /> __arm64_sys_sendto+0x30/0x40<br /> invoke_syscall+0x50/0x120<br /> el0_svc_common.constprop.0+0x170/0x194<br /> do_el0_svc+0x38/0x4c<br /> el0_svc+0x28/0xe0<br /> el0t_64_sync_handler+0xbc/0x13c<br /> el0t_64_sync+0x180/0x184<br /> <br /> Get softirq info by bcc tool:<br /> ./softirqs -NT 10<br /> Tracing soft irq event time... Hit Ctrl-C to end.<br /> <br /> 15:34:34<br /> SOFTIRQ TOTAL_nsecs<br /> block 158990<br /> timer 20030920<br /> sched 46577080<br /> net_rx 676746820<br /> tasklet 9906067650<br /> <br /> 15:34:45<br /> SOFTIRQ TOTAL_nsecs<br /> block 86100<br /> sched 38849790<br /> net_rx <br /> ---truncated---

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/rockchip: lvds: fix PM usage counter unbalance in poweron<br /> <br /> pm_runtime_get_sync will increment pm usage counter even it failed.<br /> Forgetting to putting operation will result in reference leak here.<br /> We fix it by replacing it with the newest pm_runtime_resume_and_get<br /> to keep usage counter balanced.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> fs/ntfs3: Validate buffer length while parsing index<br /> <br /> indx_read is called when we have some NTFS directory operations that<br /> need more information from the index buffers. This adds a sanity check<br /> to make sure the returned index buffer length is legit, or we may have<br /> some out-of-bound memory accesses.<br /> <br /> [ 560.897595] BUG: KASAN: slab-out-of-bounds in hdr_find_e.isra.0+0x10c/0x320<br /> [ 560.898321] Read of size 2 at addr ffff888009497238 by task exp/245<br /> [ 560.898760]<br /> [ 560.899129] CPU: 0 PID: 245 Comm: exp Not tainted 6.0.0-rc6 #37<br /> [ 560.899505] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014<br /> [ 560.900170] Call Trace:<br /> [ 560.900407] <br /> [ 560.900732] dump_stack_lvl+0x49/0x63<br /> [ 560.901108] print_report.cold+0xf5/0x689<br /> [ 560.901395] ? hdr_find_e.isra.0+0x10c/0x320<br /> [ 560.901716] kasan_report+0xa7/0x130<br /> [ 560.901950] ? hdr_find_e.isra.0+0x10c/0x320<br /> [ 560.902208] __asan_load2+0x68/0x90<br /> [ 560.902427] hdr_find_e.isra.0+0x10c/0x320<br /> [ 560.902846] ? cmp_uints+0xe0/0xe0<br /> [ 560.903363] ? cmp_sdh+0x90/0x90<br /> [ 560.903883] ? ntfs_bread_run+0x190/0x190<br /> [ 560.904196] ? rwsem_down_read_slowpath+0x750/0x750<br /> [ 560.904969] ? ntfs_fix_post_read+0xe0/0x130<br /> [ 560.905259] ? __kasan_check_write+0x14/0x20<br /> [ 560.905599] ? up_read+0x1a/0x90<br /> [ 560.905853] ? indx_read+0x22c/0x380<br /> [ 560.906096] indx_find+0x2ef/0x470<br /> [ 560.906352] ? indx_find_buffer+0x2d0/0x2d0<br /> [ 560.906692] ? __kasan_kmalloc+0x88/0xb0<br /> [ 560.906977] dir_search_u+0x196/0x2f0<br /> [ 560.907220] ? ntfs_nls_to_utf16+0x450/0x450<br /> [ 560.907464] ? __kasan_check_write+0x14/0x20<br /> [ 560.907747] ? mutex_lock+0x8f/0xe0<br /> [ 560.907970] ? __mutex_lock_slowpath+0x20/0x20<br /> [ 560.908214] ? kmem_cache_alloc+0x143/0x4b0<br /> [ 560.908459] ntfs_lookup+0xe0/0x100<br /> [ 560.908788] __lookup_slow+0x116/0x220<br /> [ 560.909050] ? lookup_fast+0x1b0/0x1b0<br /> [ 560.909309] ? lookup_fast+0x13f/0x1b0<br /> [ 560.909601] walk_component+0x187/0x230<br /> [ 560.909944] link_path_walk.part.0+0x3f0/0x660<br /> [ 560.910285] ? handle_lookup_down+0x90/0x90<br /> [ 560.910618] ? path_init+0x642/0x6e0<br /> [ 560.911084] ? percpu_counter_add_batch+0x6e/0xf0<br /> [ 560.912559] ? __alloc_file+0x114/0x170<br /> [ 560.913008] path_openat+0x19c/0x1d10<br /> [ 560.913419] ? getname_flags+0x73/0x2b0<br /> [ 560.913815] ? kasan_save_stack+0x3a/0x50<br /> [ 560.914125] ? kasan_save_stack+0x26/0x50<br /> [ 560.914542] ? __kasan_slab_alloc+0x6d/0x90<br /> [ 560.914924] ? kmem_cache_alloc+0x143/0x4b0<br /> [ 560.915339] ? getname_flags+0x73/0x2b0<br /> [ 560.915647] ? getname+0x12/0x20<br /> [ 560.916114] ? __x64_sys_open+0x4c/0x60<br /> [ 560.916460] ? path_lookupat.isra.0+0x230/0x230<br /> [ 560.916867] ? __isolate_free_page+0x2e0/0x2e0<br /> [ 560.917194] do_filp_open+0x15c/0x1f0<br /> [ 560.917448] ? may_open_dev+0x60/0x60<br /> [ 560.917696] ? expand_files+0xa4/0x3a0<br /> [ 560.917923] ? __kasan_check_write+0x14/0x20<br /> [ 560.918185] ? _raw_spin_lock+0x88/0xdb<br /> [ 560.918409] ? _raw_spin_lock_irqsave+0x100/0x100<br /> [ 560.918783] ? _find_next_bit+0x4a/0x130<br /> [ 560.919026] ? _raw_spin_unlock+0x19/0x40<br /> [ 560.919276] ? alloc_fd+0x14b/0x2d0<br /> [ 560.919635] do_sys_openat2+0x32a/0x4b0<br /> [ 560.920035] ? file_open_root+0x230/0x230<br /> [ 560.920336] ? __rcu_read_unlock+0x5b/0x280<br /> [ 560.920813] do_sys_open+0x99/0xf0<br /> [ 560.921208] ? filp_open+0x60/0x60<br /> [ 560.921482] ? exit_to_user_mode_prepare+0x49/0x180<br /> [ 560.921867] __x64_sys_open+0x4c/0x60<br /> [ 560.922128] do_syscall_64+0x3b/0x90<br /> [ 560.922369] entry_SYSCALL_64_after_hwframe+0x63/0xcd<br /> [ 560.923030] RIP: 0033:0x7f7dff2e4469<br /> [ 560.923681] Code: 00 f3 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 088<br /> [ 560.924451] RSP: 002b:00007ffd41a210b8 EFLAGS: 00000206 ORIG_RAX: 0000000000000002<br /> [ 560.925168] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f7dff2e4469<br /> [ 560.925655] RDX: 0000000000000000 RSI: 0000000000000002 RDI:<br /> ---truncated---

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net/mlx5: Lag, fix failure to cancel delayed bond work<br /> <br /> Commit 0d4e8ed139d8 ("net/mlx5: Lag, avoid lockdep warnings")<br /> accidentally removed a call to cancel delayed bond work thus it may<br /> cause queued delay to expire and fall on an already destroyed work<br /> queue.<br /> <br /> Fix by restoring the call cancel_delayed_work_sync() before<br /> destroying the workqueue.<br /> <br /> This prevents call trace such as this:<br /> <br /> [ 329.230417] BUG: kernel NULL pointer dereference, address: 0000000000000000<br /> [ 329.231444] #PF: supervisor write access in kernel mode<br /> [ 329.232233] #PF: error_code(0x0002) - not-present page<br /> [ 329.233007] PGD 0 P4D 0<br /> [ 329.233476] Oops: 0002 [#1] SMP<br /> [ 329.234012] CPU: 5 PID: 145 Comm: kworker/u20:4 Tainted: G OE 6.0.0-rc5_mlnx #1<br /> [ 329.235282] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014<br /> [ 329.236868] Workqueue: mlx5_cmd_0000:08:00.1 cmd_work_handler [mlx5_core]<br /> [ 329.237886] RIP: 0010:_raw_spin_lock+0xc/0x20<br /> [ 329.238585] Code: f0 0f b1 17 75 02 f3 c3 89 c6 e9 6f 3c 5f ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 0f 1f 44 00 00 31 c0 ba 01 00 00 00 0f b1 17 75 02 f3 c3 89 c6 e9 45 3c 5f ff 0f 1f 44 00 00 0f 1f<br /> [ 329.241156] RSP: 0018:ffffc900001b0e98 EFLAGS: 00010046<br /> [ 329.241940] RAX: 0000000000000000 RBX: ffffffff82374ae0 RCX: 0000000000000000<br /> [ 329.242954] RDX: 0000000000000001 RSI: 0000000000000014 RDI: 0000000000000000<br /> [ 329.243974] RBP: ffff888106ccf000 R08: ffff8881004000c8 R09: ffff888100400000<br /> [ 329.244990] R10: 0000000000000000 R11: ffffffff826669f8 R12: 0000000000002000<br /> [ 329.246009] R13: 0000000000000005 R14: ffff888100aa7ce0 R15: ffff88852ca80000<br /> [ 329.247030] FS: 0000000000000000(0000) GS:ffff88852ca80000(0000) knlGS:0000000000000000<br /> [ 329.248260] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> [ 329.249111] CR2: 0000000000000000 CR3: 000000016d675001 CR4: 0000000000770ee0<br /> [ 329.250133] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000<br /> [ 329.251152] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400<br /> [ 329.252176] PKRU: 55555554

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/vmwgfx: Validate the box size for the snooped cursor<br /> <br /> Invalid userspace dma surface copies could potentially overflow<br /> the memcpy from the surface to the snooped image leading to crashes.<br /> To fix it the dimensions of the copybox have to be validated<br /> against the expected size of the snooped cursor.