Vulnerabilidades

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> arm64: ftrace: fix module PLTs with mcount<br /> <br /> Li Huafei reports that mcount-based ftrace with module PLTs was broken<br /> by commit:<br /> <br /> a6253579977e4c6f ("arm64: ftrace: consistently handle PLTs.")<br /> <br /> When a module PLTs are used and a module is loaded sufficiently far away<br /> from the kernel, we&amp;#39;ll create PLTs for any branches which are<br /> out-of-range. These are separate from the special ftrace trampoline<br /> PLTs, which the module PLT code doesn&amp;#39;t directly manipulate.<br /> <br /> When mcount is in use this is a problem, as each mcount callsite in a<br /> module will be initialized to point to a module PLT, but since commit<br /> a6253579977e4c6f ftrace_make_nop() will assume that the callsite has<br /> been initialized to point to the special ftrace trampoline PLT, and<br /> ftrace_find_callable_addr() rejects other cases.<br /> <br /> This means that when ftrace tries to initialize a callsite via<br /> ftrace_make_nop(), the call to ftrace_find_callable_addr() will find<br /> that the `_mcount` stub is out-of-range and is not handled by the ftrace<br /> PLT, resulting in a splat:<br /> <br /> | ftrace_test: loading out-of-tree module taints kernel.<br /> | ftrace: no module PLT for _mcount<br /> | ------------[ ftrace bug ]------------<br /> | ftrace failed to modify<br /> | [] 0xffff800029180014<br /> | actual: 44:00:00:94<br /> | Initializing ftrace call sites<br /> | ftrace record flags: 2000000<br /> | (0)<br /> | expected tramp: ffff80000802eb3c<br /> | ------------[ cut here ]------------<br /> | WARNING: CPU: 3 PID: 157 at kernel/trace/ftrace.c:2120 ftrace_bug+0x94/0x270<br /> | Modules linked in:<br /> | CPU: 3 PID: 157 Comm: insmod Tainted: G O 6.0.0-rc6-00151-gcd722513a189-dirty #22<br /> | Hardware name: linux,dummy-virt (DT)<br /> | pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)<br /> | pc : ftrace_bug+0x94/0x270<br /> | lr : ftrace_bug+0x21c/0x270<br /> | sp : ffff80000b2bbaf0<br /> | x29: ffff80000b2bbaf0 x28: 0000000000000000 x27: ffff0000c4d38000<br /> | x26: 0000000000000001 x25: ffff800009d7e000 x24: ffff0000c4d86e00<br /> | x23: 0000000002000000 x22: ffff80000a62b000 x21: ffff8000098ebea8<br /> | x20: ffff0000c4d38000 x19: ffff80000aa24158 x18: ffffffffffffffff<br /> | x17: 0000000000000000 x16: 0a0d2d2d2d2d2d2d x15: ffff800009aa9118<br /> | x14: 0000000000000000 x13: 6333626532303830 x12: 3030303866666666<br /> | x11: 203a706d61727420 x10: 6465746365707865 x9 : 3362653230383030<br /> | x8 : c0000000ffffefff x7 : 0000000000017fe8 x6 : 000000000000bff4<br /> | x5 : 0000000000057fa8 x4 : 0000000000000000 x3 : 0000000000000001<br /> | x2 : ad2cb14bb5438900 x1 : 0000000000000000 x0 : 0000000000000022<br /> | Call trace:<br /> | ftrace_bug+0x94/0x270<br /> | ftrace_process_locs+0x308/0x430<br /> | ftrace_module_init+0x44/0x60<br /> | load_module+0x15b4/0x1ce8<br /> | __do_sys_init_module+0x1ec/0x238<br /> | __arm64_sys_init_module+0x24/0x30<br /> | invoke_syscall+0x54/0x118<br /> | el0_svc_common.constprop.4+0x84/0x100<br /> | do_el0_svc+0x3c/0xd0<br /> | el0_svc+0x1c/0x50<br /> | el0t_64_sync_handler+0x90/0xb8<br /> | el0t_64_sync+0x15c/0x160<br /> | ---[ end trace 0000000000000000 ]---<br /> | ---------test_init-----------<br /> <br /> Fix this by reverting to the old behaviour of ignoring the old<br /> instruction when initialising an mcount callsite in a module, which was<br /> the behaviour prior to commit a6253579977e4c6f.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> dm thin: Fix UAF in run_timer_softirq()<br /> <br /> When dm_resume() and dm_destroy() are concurrent, it will<br /> lead to UAF, as follows:<br /> <br /> BUG: KASAN: use-after-free in __run_timers+0x173/0x710<br /> Write of size 8 at addr ffff88816d9490f0 by task swapper/0/0<br /> <br /> Call Trace:<br /> <br /> dump_stack_lvl+0x73/0x9f<br /> print_report.cold+0x132/0xaa2<br /> _raw_spin_lock_irqsave+0xcd/0x160<br /> __run_timers+0x173/0x710<br /> kasan_report+0xad/0x110<br /> __run_timers+0x173/0x710<br /> __asan_store8+0x9c/0x140<br /> __run_timers+0x173/0x710<br /> call_timer_fn+0x310/0x310<br /> pvclock_clocksource_read+0xfa/0x250<br /> kvm_clock_read+0x2c/0x70<br /> kvm_clock_get_cycles+0xd/0x20<br /> ktime_get+0x5c/0x110<br /> lapic_next_event+0x38/0x50<br /> clockevents_program_event+0xf1/0x1e0<br /> run_timer_softirq+0x49/0x90<br /> __do_softirq+0x16e/0x62c<br /> __irq_exit_rcu+0x1fa/0x270<br /> irq_exit_rcu+0x12/0x20<br /> sysvec_apic_timer_interrupt+0x8e/0xc0<br /> <br /> One of the concurrency UAF can be shown as below:<br /> <br /> use free<br /> do_resume |<br /> __find_device_hash_cell |<br /> dm_get |<br /> atomic_inc(&amp;md-&gt;holders) |<br /> | dm_destroy<br /> | __dm_destroy<br /> | if (!dm_suspended_md(md))<br /> | atomic_read(&amp;md-&gt;holders)<br /> | msleep(1)<br /> dm_resume |<br /> __dm_resume |<br /> dm_table_resume_targets |<br /> pool_resume |<br /> do_waker #add delay work |<br /> dm_put |<br /> atomic_dec(&amp;md-&gt;holders) |<br /> | dm_table_destroy<br /> | pool_dtr<br /> | __pool_dec<br /> | __pool_destroy<br /> | destroy_workqueue<br /> | kfree(pool) # free pool<br /> time out<br /> __do_softirq<br /> run_timer_softirq # pool has already been freed<br /> <br /> This can be easily reproduced using:<br /> 1. create thin-pool<br /> 2. dmsetup suspend pool<br /> 3. dmsetup resume pool<br /> 4. dmsetup remove_all # Concurrent with 3<br /> <br /> The root cause of this UAF bug is that dm_resume() adds timer after<br /> dm_destroy() skips cancelling the timer because of suspend status.<br /> After timeout, it will call run_timer_softirq(), however pool has<br /> already been freed. The concurrency UAF bug will happen.<br /> <br /> Therefore, cancelling timer again in __pool_destroy().

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> s390/netiucv: Fix return type of netiucv_tx()<br /> <br /> With clang&amp;#39;s kernel control flow integrity (kCFI, CONFIG_CFI_CLANG),<br /> indirect call targets are validated against the expected function<br /> pointer prototype to make sure the call target is valid to help mitigate<br /> ROP attacks. If they are not identical, there is a failure at run time,<br /> which manifests as either a kernel panic or thread getting killed. A<br /> proposed warning in clang aims to catch these at compile time, which<br /> reveals:<br /> <br /> drivers/s390/net/netiucv.c:1854:21: error: incompatible function pointer types initializing &amp;#39;netdev_tx_t (*)(struct sk_buff *, struct net_device *)&amp;#39; (aka &amp;#39;enum netdev_tx (*)(struct sk_buff *, struct net_device *)&amp;#39;) with an expression of type &amp;#39;int (struct sk_buff *, struct net_device *)&amp;#39; [-Werror,-Wincompatible-function-pointer-types-strict]<br /> .ndo_start_xmit = netiucv_tx,<br /> ^~~~~~~~~~<br /> <br /> -&gt;ndo_start_xmit() in &amp;#39;struct net_device_ops&amp;#39; expects a return type of<br /> &amp;#39;netdev_tx_t&amp;#39;, not &amp;#39;int&amp;#39;. Adjust the return type of netiucv_tx() to<br /> match the prototype&amp;#39;s to resolve the warning and potential CFI failure,<br /> should s390 select ARCH_SUPPORTS_CFI_CLANG in the future.<br /> <br /> Additionally, while in the area, remove a comment block that is no<br /> longer relevant.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: plfxlc: fix potential memory leak in __lf_x_usb_enable_rx()<br /> <br /> urbs does not be freed in exception paths in __lf_x_usb_enable_rx().<br /> That will trigger memory leak. To fix it, add kfree() for urbs within<br /> "error" label. Compile tested only.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> mtd: Fix device name leak when register device failed in add_mtd_device()<br /> <br /> There is a kmemleak when register device failed:<br /> unreferenced object 0xffff888101aab550 (size 8):<br /> comm "insmod", pid 3922, jiffies 4295277753 (age 925.408s)<br /> hex dump (first 8 bytes):<br /> 6d 74 64 30 00 88 ff ff mtd0....<br /> backtrace:<br /> [] __kmalloc_node_track_caller+0x4e/0x150<br /> [] kvasprintf+0xb0/0x130<br /> [] kobject_set_name_vargs+0x2f/0xb0<br /> [] dev_set_name+0xab/0xe0<br /> [] add_mtd_device+0x4bb/0x700<br /> [] mtd_device_parse_register+0x2ac/0x3f0<br /> [] 0xffffffffa0238457<br /> [] 0xffffffffa02a008f<br /> [] do_one_initcall+0x87/0x2a0<br /> [] do_init_module+0xdf/0x320<br /> [] load_module+0x2f98/0x3330<br /> [] __do_sys_finit_module+0x113/0x1b0<br /> [] do_syscall_64+0x35/0x80<br /> [] entry_SYSCALL_64_after_hwframe+0x46/0xb0<br /> <br /> If register device failed, should call put_device() to give up the<br /> reference.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> fs: jfs: fix shift-out-of-bounds in dbAllocAG<br /> <br /> Syzbot found a crash : UBSAN: shift-out-of-bounds in dbAllocAG. The<br /> underlying bug is the missing check of bmp-&gt;db_agl2size. The field can<br /> be greater than 64 and trigger the shift-out-of-bounds.<br /> <br /> Fix this bug by adding a check of bmp-&gt;db_agl2size in dbMount since this<br /> field is used in many following functions. The upper bound for this<br /> field is L2MAXL2SIZE - L2MAXAG, thanks for the help of Dave Kleikamp.<br /> Note that, for maintenance, I reorganized error handling code of dbMount.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> usb: gadget: f_hid: fix f_hidg lifetime vs cdev<br /> <br /> The embedded struct cdev does not have its lifetime correctly tied to<br /> the enclosing struct f_hidg, so there is a use-after-free if /dev/hidgN<br /> is held open while the gadget is deleted.<br /> <br /> This can readily be replicated with libusbgx&amp;#39;s example programs (for<br /> conciseness - operating directly via configfs is equivalent):<br /> <br /> gadget-hid<br /> exec 3 /dev/hidg0<br /> gadget-vid-pid-remove<br /> exec 3

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> xfrm: Update ipcomp_scratches with NULL when freed<br /> <br /> Currently if ipcomp_alloc_scratches() fails to allocate memory<br /> ipcomp_scratches holds obsolete address. So when we try to free the<br /> percpu scratches using ipcomp_free_scratches() it tries to vfree non<br /> existent vm area. Described below:<br /> <br /> static void * __percpu *ipcomp_alloc_scratches(void)<br /> {<br /> ...<br /> scratches = alloc_percpu(void *);<br /> if (!scratches)<br /> return NULL;<br /> ipcomp_scratches does not know about this allocation failure.<br /> Therefore holding the old obsolete address.<br /> ...<br /> }<br /> <br /> So when we free,<br /> <br /> static void ipcomp_free_scratches(void)<br /> {<br /> ...<br /> scratches = ipcomp_scratches;<br /> Assigning obsolete address from ipcomp_scratches<br /> <br /> if (!scratches)<br /> return;<br /> <br /> for_each_possible_cpu(i)<br /> vfree(*per_cpu_ptr(scratches, i));<br /> Trying to free non existent page, causing warning: trying to vfree<br /> existent vm area.<br /> ...<br /> }<br /> <br /> Fix this breakage by updating ipcomp_scrtches with NULL when scratches<br /> is freed

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> platform/chrome: fix memory corruption in ioctl<br /> <br /> If "s_mem.bytes" is larger than the buffer size it leads to memory<br /> corruption.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> pinctrl: thunderbay: fix possible memory leak in thunderbay_build_functions()<br /> <br /> The thunderbay_add_functions() will free memory of thunderbay_funcs<br /> when everything is ok, but thunderbay_funcs will not be freed when<br /> thunderbay_add_functions() fails, then there will be a memory leak,<br /> so we need to add kfree() when thunderbay_add_functions() fails to<br /> fix it.<br /> <br /> In addition, doing some cleaner works, moving kfree(funcs) from<br /> thunderbay_add_functions() to thunderbay_build_functions().

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> regmap-irq: Use the new num_config_regs property in regmap_add_irq_chip_fwnode<br /> <br /> Commit faa87ce9196d ("regmap-irq: Introduce config registers for irq<br /> types") added the num_config_regs, then commit 9edd4f5aee84 ("regmap-irq:<br /> Deprecate type registers and virtual registers") suggested to replace<br /> num_type_reg with it. However, regmap_add_irq_chip_fwnode wasn&amp;#39;t modified<br /> to use the new property. Later on, commit 255a03bb1bb3 ("ASoC: wcd9335:<br /> Convert irq chip to config regs") removed the old num_type_reg property<br /> from the WCD9335 driver&amp;#39;s struct regmap_irq_chip, causing a null pointer<br /> dereference in regmap_irq_set_type when it tried to index d-&gt;type_buf as<br /> it was never allocated in regmap_add_irq_chip_fwnode:<br /> <br /> [ 39.199374] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000<br /> <br /> [ 39.200006] Call trace:<br /> [ 39.200014] regmap_irq_set_type+0x84/0x1c0<br /> [ 39.200026] __irq_set_trigger+0x60/0x1c0<br /> [ 39.200040] __setup_irq+0x2f4/0x78c<br /> [ 39.200051] request_threaded_irq+0xe8/0x1a0<br /> <br /> Use num_config_regs in regmap_add_irq_chip_fwnode instead of num_type_reg,<br /> and fall back to it if num_config_regs isn&amp;#39;t defined to maintain backward<br /> compatibility.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> clk: imx: scu: fix memleak on platform_device_add() fails<br /> <br /> No error handling is performed when platform_device_add()<br /> fails. Add error processing before return, and modified<br /> the return value.