Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> blk-mq: Fix kmemleak in blk_mq_init_allocated_queue<br /> <br /> There is a kmemleak caused by modprobe null_blk.ko<br /> <br /> unreferenced object 0xffff8881acb1f000 (size 1024):<br /> comm "modprobe", pid 836, jiffies 4294971190 (age 27.068s)<br /> hex dump (first 32 bytes):<br /> 00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00 .....N..........<br /> ff ff ff ff ff ff ff ff 00 53 99 9e ff ff ff ff .........S......<br /> backtrace:<br /> [] kmalloc_node_trace+0x22/0x60<br /> [] blk_mq_alloc_and_init_hctx+0x289/0x350<br /> [] blk_mq_realloc_hw_ctxs+0x2fe/0x3d0<br /> [] blk_mq_init_allocated_queue+0x48c/0x1440<br /> [] __blk_mq_alloc_disk+0xc8/0x1c0<br /> [] 0xffffffffc450d69d<br /> [] 0xffffffffc4538392<br /> [] do_one_initcall+0xd0/0x4f0<br /> [] do_init_module+0x1a4/0x680<br /> [] load_module+0x6249/0x7110<br /> [] __do_sys_finit_module+0x140/0x200<br /> [] do_syscall_64+0x35/0x80<br /> [] entry_SYSCALL_64_after_hwframe+0x46/0xb0<br /> <br /> That is because q-&gt;ma_ops is set to NULL before blk_release_queue is<br /> called.<br /> <br /> blk_mq_init_queue_data<br /> blk_mq_init_allocated_queue<br /> blk_mq_realloc_hw_ctxs<br /> for (i = 0; i nr_hw_queues; i++) {<br /> old_hctx = xa_load(&amp;q-&gt;hctx_table, i);<br /> if (!blk_mq_alloc_and_init_hctx(.., i, ..)) [1]<br /> if (!old_hctx)<br /> break;<br /> <br /> xa_for_each_start(&amp;q-&gt;hctx_table, j, hctx, j)<br /> blk_mq_exit_hctx(q, set, hctx, j); [2]<br /> <br /> if (!q-&gt;nr_hw_queues) [3]<br /> goto err_hctxs;<br /> <br /> err_exit:<br /> q-&gt;mq_ops = NULL; [4]<br /> <br /> blk_put_queue<br /> blk_release_queue<br /> if (queue_is_mq(q)) [5]<br /> blk_mq_release(q);<br /> <br /> [1]: blk_mq_alloc_and_init_hctx failed at i != 0.<br /> [2]: The hctxs allocated by [1] are moved to q-&gt;unused_hctx_list and<br /> will be cleaned up in blk_mq_release.<br /> [3]: q-&gt;nr_hw_queues is 0.<br /> [4]: Set q-&gt;mq_ops to NULL.<br /> [5]: queue_is_mq returns false due to [4]. And blk_mq_release<br /> will not be called. The hctxs in q-&gt;unused_hctx_list are leaked.<br /> <br /> To fix it, call blk_release_queue in exception path.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> block: Fix possible memory leak for rq_wb on add_disk failure<br /> <br /> kmemleak reported memory leaks in device_add_disk():<br /> <br /> kmemleak: 3 new suspected memory leaks<br /> <br /> unreferenced object 0xffff88800f420800 (size 512):<br /> comm "modprobe", pid 4275, jiffies 4295639067 (age 223.512s)<br /> hex dump (first 32 bytes):<br /> 04 00 00 00 08 00 00 00 01 00 00 00 00 00 00 00 ................<br /> 00 e1 f5 05 00 00 00 00 00 00 00 00 00 00 00 00 ................<br /> backtrace:<br /> [] kmalloc_trace+0x26/0x60<br /> [] wbt_init+0x50/0x6f0<br /> [] wbt_enable_default+0x157/0x1c0<br /> [] blk_register_queue+0x2a4/0x420<br /> [] device_add_disk+0x6fd/0xe40<br /> [] nbd_dev_add+0x828/0xbf0 [nbd]<br /> ...<br /> <br /> It is because the memory allocated in wbt_enable_default() is not<br /> released in device_add_disk() error path.<br /> Normally, these memory are freed in:<br /> <br /> del_gendisk()<br /> rq_qos_exit()<br /> rqos-&gt;ops-&gt;exit(rqos);<br /> wbt_exit()<br /> <br /> So rq_qos_exit() is called to free the rq_wb memory for wbt_init().<br /> However in the error path of device_add_disk(), only<br /> blk_unregister_queue() is called and make rq_wb memory leaked.<br /> <br /> Add rq_qos_exit() to the error path to fix it.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net, neigh: Fix null-ptr-deref in neigh_table_clear()<br /> <br /> When IPv6 module gets initialized but hits an error in the middle,<br /> kenel panic with:<br /> <br /> KASAN: null-ptr-deref in range [0x0000000000000598-0x000000000000059f]<br /> CPU: 1 PID: 361 Comm: insmod<br /> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)<br /> RIP: 0010:__neigh_ifdown.isra.0+0x24b/0x370<br /> RSP: 0018:ffff888012677908 EFLAGS: 00000202<br /> ...<br /> Call Trace:<br /> <br /> neigh_table_clear+0x94/0x2d0<br /> ndisc_cleanup+0x27/0x40 [ipv6]<br /> inet6_init+0x21c/0x2cb [ipv6]<br /> do_one_initcall+0xd3/0x4d0<br /> do_init_module+0x1ae/0x670<br /> ...<br /> Kernel panic - not syncing: Fatal exception<br /> <br /> When ipv6 initialization fails, it will try to cleanup and calls:<br /> <br /> neigh_table_clear()<br /> neigh_ifdown(tbl, NULL)<br /> pneigh_queue_purge(&amp;tbl-&gt;proxy_queue, dev_net(dev == NULL))<br /> # dev_net(NULL) triggers null-ptr-deref.<br /> <br /> Fix it by passing NULL to pneigh_queue_purge() in neigh_ifdown() if dev<br /> is NULL, to make kernel not panic immediately.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ibmvnic: Free rwi on reset success<br /> <br /> Free the rwi structure in the event that the last rwi in the list<br /> processed successfully. The logic in commit 4f408e1fa6e1 ("ibmvnic:<br /> retry reset if there are no other resets") introduces an issue that<br /> results in a 32 byte memory leak whenever the last rwi in the list<br /> gets processed.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> Bluetooth: L2CAP: Fix memory leak in vhci_write<br /> <br /> Syzkaller reports a memory leak as follows:<br /> ====================================<br /> BUG: memory leak<br /> unreferenced object 0xffff88810d81ac00 (size 240):<br /> [...]<br /> hex dump (first 32 bytes):<br /> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................<br /> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................<br /> backtrace:<br /> [] __alloc_skb+0x1f9/0x270 net/core/skbuff.c:418<br /> [] alloc_skb include/linux/skbuff.h:1257 [inline]<br /> [] bt_skb_alloc include/net/bluetooth/bluetooth.h:469 [inline]<br /> [] vhci_get_user drivers/bluetooth/hci_vhci.c:391 [inline]<br /> [] vhci_write+0x5f/0x230 drivers/bluetooth/hci_vhci.c:511<br /> [] call_write_iter include/linux/fs.h:2192 [inline]<br /> [] new_sync_write fs/read_write.c:491 [inline]<br /> [] vfs_write+0x42d/0x540 fs/read_write.c:578<br /> [] ksys_write+0x9d/0x160 fs/read_write.c:631<br /> [] do_syscall_x64 arch/x86/entry/common.c:50 [inline]<br /> [] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80<br /> [] entry_SYSCALL_64_after_hwframe+0x63/0xcd<br /> ====================================<br /> <br /> HCI core will uses hci_rx_work() to process frame, which is queued to<br /> the hdev-&gt;rx_q tail in hci_recv_frame() by HCI driver.<br /> <br /> Yet the problem is that, HCI core may not free the skb after handling<br /> ACL data packets. To be more specific, when start fragment does not<br /> contain the L2CAP length, HCI core just copies skb into conn-&gt;rx_skb and<br /> finishes frame process in l2cap_recv_acldata(), without freeing the skb,<br /> which triggers the above memory leak.<br /> <br /> This patch solves it by releasing the relative skb, after processing<br /> the above case in l2cap_recv_acldata().

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> i2c: piix4: Fix adapter not be removed in piix4_remove()<br /> <br /> In piix4_probe(), the piix4 adapter will be registered in:<br /> <br /> piix4_probe()<br /> piix4_add_adapters_sb800() / piix4_add_adapter()<br /> i2c_add_adapter()<br /> <br /> Based on the probed device type, piix4_add_adapters_sb800() or single<br /> piix4_add_adapter() will be called.<br /> For the former case, piix4_adapter_count is set as the number of adapters,<br /> while for antoher case it is not set and kept default *zero*.<br /> <br /> When piix4 is removed, piix4_remove() removes the adapters added in<br /> piix4_probe(), basing on the piix4_adapter_count value.<br /> Because the count is zero for the single adapter case, the adapter won&amp;#39;t<br /> be removed and makes the sources allocated for adapter leaked, such as<br /> the i2c client and device.<br /> <br /> These sources can still be accessed by i2c or bus and cause problems.<br /> An easily reproduced case is that if a new adapter is registered, i2c<br /> will get the leaked adapter and try to call smbus_algorithm, which was<br /> already freed:<br /> <br /> Triggered by: rmmod i2c_piix4 &amp;&amp; modprobe max31730<br /> <br /> BUG: unable to handle page fault for address: ffffffffc053d860<br /> #PF: supervisor read access in kernel mode<br /> #PF: error_code(0x0000) - not-present page<br /> Oops: 0000 [#1] PREEMPT SMP KASAN<br /> CPU: 0 PID: 3752 Comm: modprobe Tainted: G<br /> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)<br /> RIP: 0010:i2c_default_probe (drivers/i2c/i2c-core-base.c:2259) i2c_core<br /> RSP: 0018:ffff888107477710 EFLAGS: 00000246<br /> ...<br /> <br /> i2c_detect (drivers/i2c/i2c-core-base.c:2302) i2c_core<br /> __process_new_driver (drivers/i2c/i2c-core-base.c:1336) i2c_core<br /> bus_for_each_dev (drivers/base/bus.c:301)<br /> i2c_for_each_dev (drivers/i2c/i2c-core-base.c:1823) i2c_core<br /> i2c_register_driver (drivers/i2c/i2c-core-base.c:1861) i2c_core<br /> do_one_initcall (init/main.c:1296)<br /> do_init_module (kernel/module/main.c:2455)<br /> ...<br /> <br /> ---[ end trace 0000000000000000 ]---<br /> <br /> Fix this problem by correctly set piix4_adapter_count as 1 for the<br /> single adapter so it can be normally removed.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: mdio: fix undefined behavior in bit shift for __mdiobus_register<br /> <br /> Shifting signed 32-bit value by 31 bits is undefined, so changing<br /> significant bit to unsigned. The UBSAN warning calltrace like below:<br /> <br /> UBSAN: shift-out-of-bounds in drivers/net/phy/mdio_bus.c:586:27<br /> left shift of 1 by 31 places cannot be represented in type &amp;#39;int&amp;#39;<br /> Call Trace:<br /> <br /> dump_stack_lvl+0x7d/0xa5<br /> dump_stack+0x15/0x1b<br /> ubsan_epilogue+0xe/0x4e<br /> __ubsan_handle_shift_out_of_bounds+0x1e7/0x20c<br /> __mdiobus_register+0x49d/0x4e0<br /> fixed_mdio_bus_init+0xd8/0x12d<br /> do_one_initcall+0x76/0x430<br /> kernel_init_freeable+0x3b3/0x422<br /> kernel_init+0x24/0x1e0<br /> ret_from_fork+0x1f/0x30<br />

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net/smc: Fix possible leaked pernet namespace in smc_init()<br /> <br /> In smc_init(), register_pernet_subsys(&amp;smc_net_stat_ops) is called<br /> without any error handling.<br /> If it fails, registering of &amp;smc_net_ops won&amp;#39;t be reverted.<br /> And if smc_nl_init() fails, &amp;smc_net_stat_ops itself won&amp;#39;t be reverted.<br /> <br /> This leaves wild ops in subsystem linkedlist and when another module<br /> tries to call register_pernet_operations() it triggers page fault:<br /> <br /> BUG: unable to handle page fault for address: fffffbfff81b964c<br /> RIP: 0010:register_pernet_operations+0x1b9/0x5f0<br /> Call Trace:<br /> <br /> register_pernet_subsys+0x29/0x40<br /> ebtables_init+0x58/0x1000 [ebtables]<br /> ...

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ipv6: fix WARNING in ip6_route_net_exit_late()<br /> <br /> During the initialization of ip6_route_net_init_late(), if file<br /> ipv6_route or rt6_stats fails to be created, the initialization is<br /> successful by default. Therefore, the ipv6_route or rt6_stats file<br /> doesn&amp;#39;t be found during the remove in ip6_route_net_exit_late(). It<br /> will cause WRNING.<br /> <br /> The following is the stack information:<br /> name &amp;#39;rt6_stats&amp;#39;<br /> WARNING: CPU: 0 PID: 9 at fs/proc/generic.c:712 remove_proc_entry+0x389/0x460<br /> Modules linked in:<br /> Workqueue: netns cleanup_net<br /> RIP: 0010:remove_proc_entry+0x389/0x460<br /> PKRU: 55555554<br /> Call Trace:<br /> <br /> ops_exit_list+0xb0/0x170<br /> cleanup_net+0x4ea/0xb00<br /> process_one_work+0x9bf/0x1710<br /> worker_thread+0x665/0x1080<br /> kthread+0x2e4/0x3a0<br /> ret_from_fork+0x1f/0x30<br />

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> capabilities: fix potential memleak on error path from vfs_getxattr_alloc()<br /> <br /> In cap_inode_getsecurity(), we will use vfs_getxattr_alloc() to<br /> complete the memory allocation of tmpbuf, if we have completed<br /> the memory allocation of tmpbuf, but failed to call handler-&gt;get(...),<br /> there will be a memleak in below logic:<br /> <br /> |-- ret = (int)vfs_getxattr_alloc(mnt_userns, ...)<br /> | /* ^^^ alloc for tmpbuf */<br /> |-- value = krealloc(*xattr_value, error + 1, flags)<br /> | /* ^^^ alloc memory */<br /> |-- error = handler-&gt;get(handler, ...)<br /> | /* error! */<br /> |-- *xattr_value = value<br /> | /* xattr_value is &amp;tmpbuf (memory leak!) */<br /> <br /> So we will try to free(tmpbuf) after vfs_getxattr_alloc() fails to fix it.<br /> <br /> [PM: subject line and backtrace tweaks]

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> tracing: kprobe: Fix memory leak in test_gen_kprobe/kretprobe_cmd()<br /> <br /> test_gen_kprobe_cmd() only free buf in fail path, hence buf will leak<br /> when there is no failure. Move kfree(buf) from fail path to common path<br /> to prevent the memleak. The same reason and solution in<br /> test_gen_kretprobe_cmd().<br /> <br /> unreferenced object 0xffff888143b14000 (size 2048):<br /> comm "insmod", pid 52490, jiffies 4301890980 (age 40.553s)<br /> hex dump (first 32 bytes):<br /> 70 3a 6b 70 72 6f 62 65 73 2f 67 65 6e 5f 6b 70 p:kprobes/gen_kp<br /> 72 6f 62 65 5f 74 65 73 74 20 64 6f 5f 73 79 73 robe_test do_sys<br /> backtrace:<br /> [] kmalloc_trace+0x27/0xa0<br /> [] 0xffffffffa059006f<br /> [] do_one_initcall+0x87/0x2a0<br /> [] do_init_module+0xdf/0x320<br /> [] load_module+0x3006/0x3390<br /> [] __do_sys_finit_module+0x113/0x1b0<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 /> ftrace: Fix use-after-free for dynamic ftrace_ops<br /> <br /> KASAN reported a use-after-free with ftrace ops [1]. It was found from<br /> vmcore that perf had registered two ops with the same content<br /> successively, both dynamic. After unregistering the second ops, a<br /> use-after-free occurred.<br /> <br /> In ftrace_shutdown(), when the second ops is unregistered, the<br /> FTRACE_UPDATE_CALLS command is not set because there is another enabled<br /> ops with the same content. Also, both ops are dynamic and the ftrace<br /> callback function is ftrace_ops_list_func, so the<br /> FTRACE_UPDATE_TRACE_FUNC command will not be set. Eventually the value<br /> of &amp;#39;command&amp;#39; will be 0 and ftrace_shutdown() will skip the rcu<br /> synchronization.<br /> <br /> However, ftrace may be activated. When the ops is released, another CPU<br /> may be accessing the ops. Add the missing synchronization to fix this<br /> problem.<br /> <br /> [1]<br /> BUG: KASAN: use-after-free in __ftrace_ops_list_func kernel/trace/ftrace.c:7020 [inline]<br /> BUG: KASAN: use-after-free in ftrace_ops_list_func+0x2b0/0x31c kernel/trace/ftrace.c:7049<br /> Read of size 8 at addr ffff56551965bbc8 by task syz-executor.2/14468<br /> <br /> CPU: 1 PID: 14468 Comm: syz-executor.2 Not tainted 5.10.0 #7<br /> Hardware name: linux,dummy-virt (DT)<br /> Call trace:<br /> dump_backtrace+0x0/0x40c arch/arm64/kernel/stacktrace.c:132<br /> show_stack+0x30/0x40 arch/arm64/kernel/stacktrace.c:196<br /> __dump_stack lib/dump_stack.c:77 [inline]<br /> dump_stack+0x1b4/0x248 lib/dump_stack.c:118<br /> print_address_description.constprop.0+0x28/0x48c mm/kasan/report.c:387<br /> __kasan_report mm/kasan/report.c:547 [inline]<br /> kasan_report+0x118/0x210 mm/kasan/report.c:564<br /> check_memory_region_inline mm/kasan/generic.c:187 [inline]<br /> __asan_load8+0x98/0xc0 mm/kasan/generic.c:253<br /> __ftrace_ops_list_func kernel/trace/ftrace.c:7020 [inline]<br /> ftrace_ops_list_func+0x2b0/0x31c kernel/trace/ftrace.c:7049<br /> ftrace_graph_call+0x0/0x4<br /> __might_sleep+0x8/0x100 include/linux/perf_event.h:1170<br /> __might_fault mm/memory.c:5183 [inline]<br /> __might_fault+0x58/0x70 mm/memory.c:5171<br /> do_strncpy_from_user lib/strncpy_from_user.c:41 [inline]<br /> strncpy_from_user+0x1f4/0x4b0 lib/strncpy_from_user.c:139<br /> getname_flags+0xb0/0x31c fs/namei.c:149<br /> getname+0x2c/0x40 fs/namei.c:209<br /> [...]<br /> <br /> Allocated by task 14445:<br /> kasan_save_stack+0x24/0x50 mm/kasan/common.c:48<br /> kasan_set_track mm/kasan/common.c:56 [inline]<br /> __kasan_kmalloc mm/kasan/common.c:479 [inline]<br /> __kasan_kmalloc.constprop.0+0x110/0x13c mm/kasan/common.c:449<br /> kasan_kmalloc+0xc/0x14 mm/kasan/common.c:493<br /> kmem_cache_alloc_trace+0x440/0x924 mm/slub.c:2950<br /> kmalloc include/linux/slab.h:563 [inline]<br /> kzalloc include/linux/slab.h:675 [inline]<br /> perf_event_alloc.part.0+0xb4/0x1350 kernel/events/core.c:11230<br /> perf_event_alloc kernel/events/core.c:11733 [inline]<br /> __do_sys_perf_event_open kernel/events/core.c:11831 [inline]<br /> __se_sys_perf_event_open+0x550/0x15f4 kernel/events/core.c:11723<br /> __arm64_sys_perf_event_open+0x6c/0x80 kernel/events/core.c:11723<br /> [...]<br /> <br /> Freed by task 14445:<br /> kasan_save_stack+0x24/0x50 mm/kasan/common.c:48<br /> kasan_set_track+0x24/0x34 mm/kasan/common.c:56<br /> kasan_set_free_info+0x20/0x40 mm/kasan/generic.c:358<br /> __kasan_slab_free.part.0+0x11c/0x1b0 mm/kasan/common.c:437<br /> __kasan_slab_free mm/kasan/common.c:445 [inline]<br /> kasan_slab_free+0x2c/0x40 mm/kasan/common.c:446<br /> slab_free_hook mm/slub.c:1569 [inline]<br /> slab_free_freelist_hook mm/slub.c:1608 [inline]<br /> slab_free mm/slub.c:3179 [inline]<br /> kfree+0x12c/0xc10 mm/slub.c:4176<br /> perf_event_alloc.part.0+0xa0c/0x1350 kernel/events/core.c:11434<br /> perf_event_alloc kernel/events/core.c:11733 [inline]<br /> __do_sys_perf_event_open kernel/events/core.c:11831 [inline]<br /> __se_sys_perf_event_open+0x550/0x15f4 kernel/events/core.c:11723<br /> [...]