Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ext4: fix bug_on in __es_tree_search caused by bad quota inode<br /> <br /> We got a issue as fllows:<br /> ==================================================================<br /> kernel BUG at fs/ext4/extents_status.c:202!<br /> invalid opcode: 0000 [#1] PREEMPT SMP<br /> CPU: 1 PID: 810 Comm: mount Not tainted 6.1.0-rc1-next-g9631525255e3 #352<br /> RIP: 0010:__es_tree_search.isra.0+0xb8/0xe0<br /> RSP: 0018:ffffc90001227900 EFLAGS: 00010202<br /> RAX: 0000000000000000 RBX: 0000000077512a0f RCX: 0000000000000000<br /> RDX: 0000000000000002 RSI: 0000000000002a10 RDI: ffff8881004cd0c8<br /> RBP: ffff888177512ac8 R08: 47ffffffffffffff R09: 0000000000000001<br /> R10: 0000000000000001 R11: 00000000000679af R12: 0000000000002a10<br /> R13: ffff888177512d88 R14: 0000000077512a10 R15: 0000000000000000<br /> FS: 00007f4bd76dbc40(0000)GS:ffff88842fd00000(0000)knlGS:0000000000000000<br /> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> CR2: 00005653bf993cf8 CR3: 000000017bfdf000 CR4: 00000000000006e0<br /> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000<br /> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400<br /> Call Trace:<br /> <br /> ext4_es_cache_extent+0xe2/0x210<br /> ext4_cache_extents+0xd2/0x110<br /> ext4_find_extent+0x5d5/0x8c0<br /> ext4_ext_map_blocks+0x9c/0x1d30<br /> ext4_map_blocks+0x431/0xa50<br /> ext4_getblk+0x82/0x340<br /> ext4_bread+0x14/0x110<br /> ext4_quota_read+0xf0/0x180<br /> v2_read_header+0x24/0x90<br /> v2_check_quota_file+0x2f/0xa0<br /> dquot_load_quota_sb+0x26c/0x760<br /> dquot_load_quota_inode+0xa5/0x190<br /> ext4_enable_quotas+0x14c/0x300<br /> __ext4_fill_super+0x31cc/0x32c0<br /> ext4_fill_super+0x115/0x2d0<br /> get_tree_bdev+0x1d2/0x360<br /> ext4_get_tree+0x19/0x30<br /> vfs_get_tree+0x26/0xe0<br /> path_mount+0x81d/0xfc0<br /> do_mount+0x8d/0xc0<br /> __x64_sys_mount+0xc0/0x160<br /> do_syscall_64+0x35/0x80<br /> entry_SYSCALL_64_after_hwframe+0x63/0xcd<br /> <br /> ==================================================================<br /> <br /> Above issue may happen as follows:<br /> -------------------------------------<br /> ext4_fill_super<br /> ext4_orphan_cleanup<br /> ext4_enable_quotas<br /> ext4_quota_enable<br /> ext4_iget --&gt; get error inode <br /> ext4_ext_check_inode --&gt; Wrong imode makes it escape inspection<br /> make_bad_inode(inode) --&gt; EXT4_BOOT_LOADER_INO set imode<br /> dquot_load_quota_inode<br /> vfs_setup_quota_inode --&gt; check pass<br /> dquot_load_quota_sb<br /> v2_check_quota_file<br /> v2_read_header<br /> ext4_quota_read<br /> ext4_bread<br /> ext4_getblk<br /> ext4_map_blocks<br /> ext4_ext_map_blocks<br /> ext4_find_extent<br /> ext4_cache_extents<br /> ext4_es_cache_extent<br /> __es_tree_search.isra.0<br /> ext4_es_end --&gt; Wrong extents trigger BUG_ON<br /> <br /> In the above issue, s_usr_quota_inum is set to 5, but inode contains<br /> incorrect imode and disordered extents. Because 5 is EXT4_BOOT_LOADER_INO,<br /> the ext4_ext_check_inode check in the ext4_iget function can be bypassed,<br /> finally, the extents that are not checked trigger the BUG_ON in the<br /> __es_tree_search function. To solve this issue, check whether the inode is<br /> bad_inode in vfs_setup_quota_inode().

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> mptcp: use proper req destructor for IPv6<br /> <br /> Before, only the destructor from TCP request sock in IPv4 was called<br /> even if the subflow was IPv6.<br /> <br /> It is important to use the right destructor to avoid memory leaks with<br /> some advanced IPv6 features, e.g. when the request socks contain<br /> specific IPv6 options.

Missing Authorization vulnerability in bnayawpguy Resoto allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Resoto: from n/a through 1.0.8.

Improper Neutralization of Input During Web Page Generation (XSS or &amp;#39;Cross-site Scripting&amp;#39;) vulnerability in Bob Hostel allows DOM-Based XSS.This issue affects Hostel: from n/a through 1.1.5.1.

Improper Neutralization of Special Elements used in an SQL Command (&amp;#39;SQL Injection&amp;#39;) vulnerability in WPJobBoard allows Blind SQL Injection.This issue affects WPJobBoard: from n/a through 5.9.0.

Missing Authorization vulnerability in Jewel Theme Master Addons for Elementor allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Master Addons for Elementor: from n/a through 2.0.5.3.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> iommufd: Do not add the same hwpt to the ioas-&gt;hwpt_list twice<br /> <br /> The hwpt is added to the hwpt_list only during its creation, it is never<br /> added again. This hunk is some missed leftover from rework. Adding it<br /> twice will corrupt the linked list in some cases.<br /> <br /> It effects HWPT specific attachment, which is something the test suite<br /> cannot cover until we can create a legitimate struct device with a<br /> non-system iommu "driver" (ie we need the bus removed from the iommu code)

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> netdevsim: fix memory leak in nsim_bus_dev_new()<br /> <br /> If device_register() failed in nsim_bus_dev_new(), the value of reference<br /> in nsim_bus_dev-&gt;dev is 1. obj-&gt;name in nsim_bus_dev-&gt;dev will not be<br /> released.<br /> <br /> unreferenced object 0xffff88810352c480 (size 16):<br /> comm "echo", pid 5691, jiffies 4294945921 (age 133.270s)<br /> hex dump (first 16 bytes):<br /> 6e 65 74 64 65 76 73 69 6d 31 00 00 00 00 00 00 netdevsim1......<br /> backtrace:<br /> [] __kmalloc_node_track_caller+0x3a/0xb0<br /> [] kvasprintf+0xc3/0x160<br /> [] kvasprintf_const+0x55/0x180<br /> [] kobject_set_name_vargs+0x56/0x150<br /> [] dev_set_name+0xbb/0xf0<br /> [] device_add+0x1f8/0x1cb0<br /> [] new_device_store+0x3b6/0x5e0<br /> [] bus_attr_store+0x72/0xa0<br /> [] sysfs_kf_write+0x106/0x160<br /> [] kernfs_fop_write_iter+0x3a8/0x5a0<br /> [] vfs_write+0x8f0/0xc80<br /> [] ksys_write+0x106/0x210<br /> [] do_syscall_64+0x35/0x80<br /> [] entry_SYSCALL_64_after_hwframe+0x46/0xb0

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ALSA: mts64: fix possible null-ptr-defer in snd_mts64_interrupt<br /> <br /> I got a null-ptr-defer error report when I do the following tests<br /> on the qemu platform:<br /> <br /> make defconfig and CONFIG_PARPORT=m, CONFIG_PARPORT_PC=m,<br /> CONFIG_SND_MTS64=m<br /> <br /> Then making test scripts:<br /> cat&gt;test_mod1.sh

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> crypto: qat - fix DMA transfer direction<br /> <br /> When CONFIG_DMA_API_DEBUG is selected, while running the crypto self<br /> test on the QAT crypto algorithms, the function add_dma_entry() reports<br /> a warning similar to the one below, saying that overlapping mappings<br /> are not supported. This occurs in tests where the input and the output<br /> scatter list point to the same buffers (i.e. two different scatter lists<br /> which point to the same chunks of memory).<br /> <br /> The logic that implements the mapping uses the flag DMA_BIDIRECTIONAL<br /> for both the input and the output scatter lists which leads to<br /> overlapped write mappings. These are not supported by the DMA layer.<br /> <br /> Fix by specifying the correct DMA transfer directions when mapping<br /> buffers. For in-place operations where the input scatter list<br /> matches the output scatter list, buffers are mapped once with<br /> DMA_BIDIRECTIONAL, otherwise input buffers are mapped using the flag<br /> DMA_TO_DEVICE and output buffers are mapped with DMA_FROM_DEVICE.<br /> Overlapping a read mapping with a write mapping is a valid case in<br /> dma-coherent devices like QAT.<br /> The function that frees and unmaps the buffers, qat_alg_free_bufl()<br /> has been changed accordingly to the changes to the mapping function.<br /> <br /> DMA-API: 4xxx 0000:06:00.0: cacheline tracking EEXIST, overlapping mappings aren&amp;#39;t supported<br /> WARNING: CPU: 53 PID: 4362 at kernel/dma/debug.c:570 add_dma_entry+0x1e9/0x270<br /> ...<br /> Call Trace:<br /> dma_map_page_attrs+0x82/0x2d0<br /> ? preempt_count_add+0x6a/0xa0<br /> qat_alg_sgl_to_bufl+0x45b/0x990 [intel_qat]<br /> qat_alg_aead_dec+0x71/0x250 [intel_qat]<br /> crypto_aead_decrypt+0x3d/0x70<br /> test_aead_vec_cfg+0x649/0x810<br /> ? number+0x310/0x3a0<br /> ? vsnprintf+0x2a3/0x550<br /> ? scnprintf+0x42/0x70<br /> ? valid_sg_divisions.constprop.0+0x86/0xa0<br /> ? test_aead_vec+0xdf/0x120<br /> test_aead_vec+0xdf/0x120<br /> alg_test_aead+0x185/0x400<br /> alg_test+0x3d8/0x500<br /> ? crypto_acomp_scomp_free_ctx+0x30/0x30<br /> ? __schedule+0x32a/0x12a0<br /> ? ttwu_queue_wakelist+0xbf/0x110<br /> ? _raw_spin_unlock_irqrestore+0x23/0x40<br /> ? try_to_wake_up+0x83/0x570<br /> ? _raw_spin_unlock_irqrestore+0x23/0x40<br /> ? __set_cpus_allowed_ptr_locked+0xea/0x1b0<br /> ? crypto_acomp_scomp_free_ctx+0x30/0x30<br /> cryptomgr_test+0x27/0x50<br /> kthread+0xe6/0x110<br /> ? kthread_complete_and_exit+0x20/0x20<br /> ret_from_fork+0x1f/0x30

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> RDMA/hns: Fix refcount leak in hns_roce_mmap<br /> <br /> rdma_user_mmap_entry_get_pgoff() takes the reference.<br /> Add missing rdma_user_mmap_entry_put() to release the reference.<br /> <br /> Acked-by Haoyue Xu

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> clk: st: Fix memory leak in st_of_quadfs_setup()<br /> <br /> If st_clk_register_quadfs_pll() fails, @lock should be freed before goto<br /> @err_exit, otherwise will cause meory leak issue, fix it.