Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> block, bfq: don&amp;#39;t move oom_bfqq<br /> <br /> Our test report a UAF:<br /> <br /> [ 2073.019181] ==================================================================<br /> [ 2073.019188] BUG: KASAN: use-after-free in __bfq_put_async_bfqq+0xa0/0x168<br /> [ 2073.019191] Write of size 8 at addr ffff8000ccf64128 by task rmmod/72584<br /> [ 2073.019192]<br /> [ 2073.019196] CPU: 0 PID: 72584 Comm: rmmod Kdump: loaded Not tainted 4.19.90-yk #5<br /> [ 2073.019198] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015<br /> [ 2073.019200] Call trace:<br /> [ 2073.019203] dump_backtrace+0x0/0x310<br /> [ 2073.019206] show_stack+0x28/0x38<br /> [ 2073.019210] dump_stack+0xec/0x15c<br /> [ 2073.019216] print_address_description+0x68/0x2d0<br /> [ 2073.019220] kasan_report+0x238/0x2f0<br /> [ 2073.019224] __asan_store8+0x88/0xb0<br /> [ 2073.019229] __bfq_put_async_bfqq+0xa0/0x168<br /> [ 2073.019233] bfq_put_async_queues+0xbc/0x208<br /> [ 2073.019236] bfq_pd_offline+0x178/0x238<br /> [ 2073.019240] blkcg_deactivate_policy+0x1f0/0x420<br /> [ 2073.019244] bfq_exit_queue+0x128/0x178<br /> [ 2073.019249] blk_mq_exit_sched+0x12c/0x160<br /> [ 2073.019252] elevator_exit+0xc8/0xd0<br /> [ 2073.019256] blk_exit_queue+0x50/0x88<br /> [ 2073.019259] blk_cleanup_queue+0x228/0x3d8<br /> [ 2073.019267] null_del_dev+0xfc/0x1e0 [null_blk]<br /> [ 2073.019274] null_exit+0x90/0x114 [null_blk]<br /> [ 2073.019278] __arm64_sys_delete_module+0x358/0x5a0<br /> [ 2073.019282] el0_svc_common+0xc8/0x320<br /> [ 2073.019287] el0_svc_handler+0xf8/0x160<br /> [ 2073.019290] el0_svc+0x10/0x218<br /> [ 2073.019291]<br /> [ 2073.019294] Allocated by task 14163:<br /> [ 2073.019301] kasan_kmalloc+0xe0/0x190<br /> [ 2073.019305] kmem_cache_alloc_node_trace+0x1cc/0x418<br /> [ 2073.019308] bfq_pd_alloc+0x54/0x118<br /> [ 2073.019313] blkcg_activate_policy+0x250/0x460<br /> [ 2073.019317] bfq_create_group_hierarchy+0x38/0x110<br /> [ 2073.019321] bfq_init_queue+0x6d0/0x948<br /> [ 2073.019325] blk_mq_init_sched+0x1d8/0x390<br /> [ 2073.019330] elevator_switch_mq+0x88/0x170<br /> [ 2073.019334] elevator_switch+0x140/0x270<br /> [ 2073.019338] elv_iosched_store+0x1a4/0x2a0<br /> [ 2073.019342] queue_attr_store+0x90/0xe0<br /> [ 2073.019348] sysfs_kf_write+0xa8/0xe8<br /> [ 2073.019351] kernfs_fop_write+0x1f8/0x378<br /> [ 2073.019359] __vfs_write+0xe0/0x360<br /> [ 2073.019363] vfs_write+0xf0/0x270<br /> [ 2073.019367] ksys_write+0xdc/0x1b8<br /> [ 2073.019371] __arm64_sys_write+0x50/0x60<br /> [ 2073.019375] el0_svc_common+0xc8/0x320<br /> [ 2073.019380] el0_svc_handler+0xf8/0x160<br /> [ 2073.019383] el0_svc+0x10/0x218<br /> [ 2073.019385]<br /> [ 2073.019387] Freed by task 72584:<br /> [ 2073.019391] __kasan_slab_free+0x120/0x228<br /> [ 2073.019394] kasan_slab_free+0x10/0x18<br /> [ 2073.019397] kfree+0x94/0x368<br /> [ 2073.019400] bfqg_put+0x64/0xb0<br /> [ 2073.019404] bfqg_and_blkg_put+0x90/0xb0<br /> [ 2073.019408] bfq_put_queue+0x220/0x228<br /> [ 2073.019413] __bfq_put_async_bfqq+0x98/0x168<br /> [ 2073.019416] bfq_put_async_queues+0xbc/0x208<br /> [ 2073.019420] bfq_pd_offline+0x178/0x238<br /> [ 2073.019424] blkcg_deactivate_policy+0x1f0/0x420<br /> [ 2073.019429] bfq_exit_queue+0x128/0x178<br /> [ 2073.019433] blk_mq_exit_sched+0x12c/0x160<br /> [ 2073.019437] elevator_exit+0xc8/0xd0<br /> [ 2073.019440] blk_exit_queue+0x50/0x88<br /> [ 2073.019443] blk_cleanup_queue+0x228/0x3d8<br /> [ 2073.019451] null_del_dev+0xfc/0x1e0 [null_blk]<br /> [ 2073.019459] null_exit+0x90/0x114 [null_blk]<br /> [ 2073.019462] __arm64_sys_delete_module+0x358/0x5a0<br /> [ 2073.019467] el0_svc_common+0xc8/0x320<br /> [ 2073.019471] el0_svc_handler+0xf8/0x160<br /> [ 2073.019474] el0_svc+0x10/0x218<br /> [ 2073.019475]<br /> [ 2073.019479] The buggy address belongs to the object at ffff8000ccf63f00<br /> which belongs to the cache kmalloc-1024 of size 1024<br /> [ 2073.019484] The buggy address is located 552 bytes inside of<br /> 1024-byte region [ffff8000ccf63f00, ffff8000ccf64300)<br /> [ 2073.019486] The buggy address belongs to the page:<br /> [ 2073.019492] page:ffff7e000333d800 count:1 mapcount:0 mapping:ffff8000c0003a00 index:0x0 compound_mapcount: 0<br /> [ 2073.020123] flags: 0x7ffff0000008100(slab|head)<br /> [ 2073.020403] raw: 07ffff0000008100 ffff7e0003334c08 ffff7e00001f5a08 ffff8000c0003a00<br /> [ 2073.020409] ra<br /> ---truncated---

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> LSM: general protection fault in legacy_parse_param<br /> <br /> The usual LSM hook "bail on fail" scheme doesn&amp;#39;t work for cases where<br /> a security module may return an error code indicating that it does not<br /> recognize an input. In this particular case Smack sees a mount option<br /> that it recognizes, and returns 0. A call to a BPF hook follows, which<br /> returns -ENOPARAM, which confuses the caller because Smack has processed<br /> its data.<br /> <br /> The SELinux hook incorrectly returns 1 on success. There was a time<br /> when this was correct, however the current expectation is that it<br /> return 0 on success. This is repaired.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: hns3: add vlan list lock to protect vlan list<br /> <br /> When adding port base VLAN, vf VLAN need to remove from HW and modify<br /> the vlan state in vf VLAN list as false. If the periodicity task is<br /> freeing the same node, it may cause "use after free" error.<br /> This patch adds a vlan list lock to protect the vlan list.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net/sched: act_ct: fix ref leak when switching zones<br /> <br /> When switching zones or network namespaces without doing a ct clear in<br /> between, it is now leaking a reference to the old ct entry. That&amp;#39;s<br /> because tcf_ct_skb_nfct_cached() returns false and<br /> tcf_ct_flow_table_lookup() may simply overwrite it.<br /> <br /> The fix is to, as the ct entry is not reusable, free it already at<br /> tcf_ct_skb_nfct_cached().

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: sparx5: switchdev: fix possible NULL pointer dereference<br /> <br /> As the possible failure of the allocation, devm_kzalloc() may return NULL<br /> pointer.<br /> Therefore, it should be better to check the &amp;#39;db&amp;#39; in order to prevent<br /> the dereference of NULL pointer.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> pinctrl: nomadik: Add missing of_node_put() in nmk_pinctrl_probe<br /> <br /> This node pointer is returned by of_parse_phandle() with refcount<br /> incremented in this function. Calling of_node_put() to avoid<br /> the refcount leak.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> clk: visconti: prevent array overflow in visconti_clk_register_gates()<br /> <br /> This code was using -1 to represent that there was no reset function.<br /> Unfortunately, the -1 was stored in u8 so the if (clks[i].rs_id &gt;= 0)<br /> condition was always true. This lead to an out of bounds access in<br /> visconti_clk_register_gates().

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> clk: Fix clk_hw_get_clk() when dev is NULL<br /> <br /> Any registered clk_core structure can have a NULL pointer in its dev<br /> field. While never actually documented, this is evidenced by the wide<br /> usage of clk_register and clk_hw_register with a NULL device pointer,<br /> and the fact that the core of_clk_hw_register() function also passes a<br /> NULL device pointer.<br /> <br /> A call to clk_hw_get_clk() on a clk_hw struct whose clk_core is in that<br /> case will result in a NULL pointer derefence when it calls dev_name() on<br /> that NULL device pointer.<br /> <br /> Add a test for this case and use NULL as the dev_id if the device<br /> pointer is NULL.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> remoteproc: qcom_q6v5_mss: Fix some leaks in q6v5_alloc_memory_region<br /> <br /> The device_node pointer is returned by of_parse_phandle() or<br /> of_get_child_by_name() with refcount incremented.<br /> We should use of_node_put() on it when done.<br /> <br /> This function only call of_node_put(node) when of_address_to_resource<br /> succeeds, missing error cases.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> clk: qcom: clk-rcg2: Update logic to calculate D value for RCG<br /> <br /> The display pixel clock has a requirement on certain newer platforms to<br /> support M/N as (2/3) and the final D value calculated results in<br /> underflow errors.<br /> As the current implementation does not check for D value is within<br /> the accepted range for a given M &amp; N value. Update the logic to<br /> calculate the final D value based on the range.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> f2fs: use spin_lock to avoid hang<br /> <br /> [14696.634553] task:cat state:D stack: 0 pid:1613738 ppid:1613735 flags:0x00000004<br /> [14696.638285] Call Trace:<br /> [14696.639038] <br /> [14696.640032] __schedule+0x302/0x930<br /> [14696.640969] schedule+0x58/0xd0<br /> [14696.641799] schedule_preempt_disabled+0x18/0x30<br /> [14696.642890] __mutex_lock.constprop.0+0x2fb/0x4f0<br /> [14696.644035] ? mod_objcg_state+0x10c/0x310<br /> [14696.645040] ? obj_cgroup_charge+0xe1/0x170<br /> [14696.646067] __mutex_lock_slowpath+0x13/0x20<br /> [14696.647126] mutex_lock+0x34/0x40<br /> [14696.648070] stat_show+0x25/0x17c0 [f2fs]<br /> [14696.649218] seq_read_iter+0x120/0x4b0<br /> [14696.650289] ? aa_file_perm+0x12a/0x500<br /> [14696.651357] ? lru_cache_add+0x1c/0x20<br /> [14696.652470] seq_read+0xfd/0x140<br /> [14696.653445] full_proxy_read+0x5c/0x80<br /> [14696.654535] vfs_read+0xa0/0x1a0<br /> [14696.655497] ksys_read+0x67/0xe0<br /> [14696.656502] __x64_sys_read+0x1a/0x20<br /> [14696.657580] do_syscall_64+0x3b/0xc0<br /> [14696.658671] entry_SYSCALL_64_after_hwframe+0x44/0xae<br /> [14696.660068] RIP: 0033:0x7efe39df1cb2<br /> [14696.661133] RSP: 002b:00007ffc8badd948 EFLAGS: 00000246 ORIG_RAX: 0000000000000000<br /> [14696.662958] RAX: ffffffffffffffda RBX: 0000000000020000 RCX: 00007efe39df1cb2<br /> [14696.664757] RDX: 0000000000020000 RSI: 00007efe399df000 RDI: 0000000000000003<br /> [14696.666542] RBP: 00007efe399df000 R08: 00007efe399de010 R09: 00007efe399de010<br /> [14696.668363] R10: 0000000000000022 R11: 0000000000000246 R12: 0000000000000000<br /> [14696.670155] R13: 0000000000000003 R14: 0000000000020000 R15: 0000000000020000<br /> [14696.671965] <br /> [14696.672826] task:umount state:D stack: 0 pid:1614985 ppid:1614984 flags:0x00004000<br /> [14696.674930] Call Trace:<br /> [14696.675903] <br /> [14696.676780] __schedule+0x302/0x930<br /> [14696.677927] schedule+0x58/0xd0<br /> [14696.679019] schedule_preempt_disabled+0x18/0x30<br /> [14696.680412] __mutex_lock.constprop.0+0x2fb/0x4f0<br /> [14696.681783] ? destroy_inode+0x65/0x80<br /> [14696.683006] __mutex_lock_slowpath+0x13/0x20<br /> [14696.684305] mutex_lock+0x34/0x40<br /> [14696.685442] f2fs_destroy_stats+0x1e/0x60 [f2fs]<br /> [14696.686803] f2fs_put_super+0x158/0x390 [f2fs]<br /> [14696.688238] generic_shutdown_super+0x7a/0x120<br /> [14696.689621] kill_block_super+0x27/0x50<br /> [14696.690894] kill_f2fs_super+0x7f/0x100 [f2fs]<br /> [14696.692311] deactivate_locked_super+0x35/0xa0<br /> [14696.693698] deactivate_super+0x40/0x50<br /> [14696.694985] cleanup_mnt+0x139/0x190<br /> [14696.696209] __cleanup_mnt+0x12/0x20<br /> [14696.697390] task_work_run+0x64/0xa0<br /> [14696.698587] exit_to_user_mode_prepare+0x1b7/0x1c0<br /> [14696.700053] syscall_exit_to_user_mode+0x27/0x50<br /> [14696.701418] do_syscall_64+0x48/0xc0<br /> [14696.702630] entry_SYSCALL_64_after_hwframe+0x44/0xae

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> f2fs: fix to do sanity check on curseg-&gt;alloc_type<br /> <br /> As Wenqing Liu reported in bugzilla:<br /> <br /> https://bugzilla.kernel.org/show_bug.cgi?id=215657<br /> <br /> - Overview<br /> UBSAN: array-index-out-of-bounds in fs/f2fs/segment.c:3460:2 when mount and operate a corrupted image<br /> <br /> - Reproduce<br /> tested on kernel 5.17-rc4, 5.17-rc6<br /> <br /> 1. mkdir test_crash<br /> 2. cd test_crash<br /> 3. unzip tmp2.zip<br /> 4. mkdir mnt<br /> 5. ./single_test.sh f2fs 2<br /> <br /> - Kernel dump<br /> [ 46.434454] loop0: detected capacity change from 0 to 131072<br /> [ 46.529839] F2FS-fs (loop0): Mounted with checkpoint version = 7548c2d9<br /> [ 46.738319] ================================================================================<br /> [ 46.738412] UBSAN: array-index-out-of-bounds in fs/f2fs/segment.c:3460:2<br /> [ 46.738475] index 231 is out of range for type &amp;#39;unsigned int [2]&amp;#39;<br /> [ 46.738539] CPU: 2 PID: 939 Comm: umount Not tainted 5.17.0-rc6 #1<br /> [ 46.738547] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-1ubuntu1.1 04/01/2014<br /> [ 46.738551] Call Trace:<br /> [ 46.738556] <br /> [ 46.738563] dump_stack_lvl+0x47/0x5c<br /> [ 46.738581] ubsan_epilogue+0x5/0x50<br /> [ 46.738592] __ubsan_handle_out_of_bounds+0x68/0x80<br /> [ 46.738604] f2fs_allocate_data_block+0xdff/0xe60 [f2fs]<br /> [ 46.738819] do_write_page+0xef/0x210 [f2fs]<br /> [ 46.738934] f2fs_do_write_node_page+0x3f/0x80 [f2fs]<br /> [ 46.739038] __write_node_page+0x2b7/0x920 [f2fs]<br /> [ 46.739162] f2fs_sync_node_pages+0x943/0xb00 [f2fs]<br /> [ 46.739293] f2fs_write_checkpoint+0x7bb/0x1030 [f2fs]<br /> [ 46.739405] kill_f2fs_super+0x125/0x150 [f2fs]<br /> [ 46.739507] deactivate_locked_super+0x60/0xc0<br /> [ 46.739517] deactivate_super+0x70/0xb0<br /> [ 46.739524] cleanup_mnt+0x11a/0x200<br /> [ 46.739532] __cleanup_mnt+0x16/0x20<br /> [ 46.739538] task_work_run+0x67/0xa0<br /> [ 46.739547] exit_to_user_mode_prepare+0x18c/0x1a0<br /> [ 46.739559] syscall_exit_to_user_mode+0x26/0x40<br /> [ 46.739568] do_syscall_64+0x46/0xb0<br /> [ 46.739584] entry_SYSCALL_64_after_hwframe+0x44/0xae<br /> <br /> The root cause is we missed to do sanity check on curseg-&gt;alloc_type,<br /> result in out-of-bound accessing on sbi-&gt;block_count[] array, fix it.