Vulnerabilidades

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drivers: serial: jsm: fix some leaks in probe<br /> <br /> This error path needs to unwind instead of just returning directly.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> cxl: Fix refcount leak in cxl_calc_capp_routing<br /> <br /> of_get_next_parent() returns a node pointer with refcount incremented,<br /> we should use of_node_put() on it when not need anymore.<br /> This function only calls of_node_put() in normal path,<br /> missing it in the error path.<br /> Add missing of_node_put() to avoid refcount leak.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ip6mr: fix UAF issue in ip6mr_sk_done() when addrconf_init_net() failed<br /> <br /> If the initialization fails in calling addrconf_init_net(), devconf_all is<br /> the pointer that has been released. Then ip6mr_sk_done() is called to<br /> release the net, accessing devconf-&gt;mc_forwarding directly causes invalid<br /> pointer access.<br /> <br /> The process is as follows:<br /> setup_net()<br /> ops_init()<br /> addrconf_init_net()<br /> all = kmemdup(...) ---&gt; alloc "all"<br /> ...<br /> net-&gt;ipv6.devconf_all = all;<br /> __addrconf_sysctl_register() ---&gt; failed<br /> ...<br /> kfree(all); ---&gt; ipv6.devconf_all invalid<br /> ...<br /> ops_exit_list()<br /> ...<br /> ip6mr_sk_done()<br /> devconf = net-&gt;ipv6.devconf_all;<br /> //devconf is invalid pointer<br /> if (!devconf || !atomic_read(&amp;devconf-&gt;mc_forwarding))<br /> <br /> The following is the Call Trace information:<br /> BUG: KASAN: use-after-free in ip6mr_sk_done+0x112/0x3a0<br /> Read of size 4 at addr ffff888075508e88 by task ip/14554<br /> Call Trace:<br /> <br /> dump_stack_lvl+0x8e/0xd1<br /> print_report+0x155/0x454<br /> kasan_report+0xba/0x1f0<br /> kasan_check_range+0x35/0x1b0<br /> ip6mr_sk_done+0x112/0x3a0<br /> rawv6_close+0x48/0x70<br /> inet_release+0x109/0x230<br /> inet6_release+0x4c/0x70<br /> sock_release+0x87/0x1b0<br /> igmp6_net_exit+0x6b/0x170<br /> ops_exit_list+0xb0/0x170<br /> setup_net+0x7ac/0xbd0<br /> copy_net_ns+0x2e6/0x6b0<br /> create_new_namespaces+0x382/0xa50<br /> unshare_nsproxy_namespaces+0xa6/0x1c0<br /> ksys_unshare+0x3a4/0x7e0<br /> __x64_sys_unshare+0x2d/0x40<br /> do_syscall_64+0x35/0x80<br /> entry_SYSCALL_64_after_hwframe+0x46/0xb0<br /> RIP: 0033:0x7f7963322547<br /> <br /> <br /> Allocated by task 14554:<br /> kasan_save_stack+0x1e/0x40<br /> kasan_set_track+0x21/0x30<br /> __kasan_kmalloc+0xa1/0xb0<br /> __kmalloc_node_track_caller+0x4a/0xb0<br /> kmemdup+0x28/0x60<br /> addrconf_init_net+0x1be/0x840<br /> ops_init+0xa5/0x410<br /> setup_net+0x5aa/0xbd0<br /> copy_net_ns+0x2e6/0x6b0<br /> create_new_namespaces+0x382/0xa50<br /> unshare_nsproxy_namespaces+0xa6/0x1c0<br /> ksys_unshare+0x3a4/0x7e0<br /> __x64_sys_unshare+0x2d/0x40<br /> do_syscall_64+0x35/0x80<br /> entry_SYSCALL_64_after_hwframe+0x46/0xb0<br /> <br /> Freed by task 14554:<br /> kasan_save_stack+0x1e/0x40<br /> kasan_set_track+0x21/0x30<br /> kasan_save_free_info+0x2a/0x40<br /> ____kasan_slab_free+0x155/0x1b0<br /> slab_free_freelist_hook+0x11b/0x220<br /> __kmem_cache_free+0xa4/0x360<br /> addrconf_init_net+0x623/0x840<br /> ops_init+0xa5/0x410<br /> setup_net+0x5aa/0xbd0<br /> copy_net_ns+0x2e6/0x6b0<br /> create_new_namespaces+0x382/0xa50<br /> unshare_nsproxy_namespaces+0xa6/0x1c0<br /> ksys_unshare+0x3a4/0x7e0<br /> __x64_sys_unshare+0x2d/0x40<br /> do_syscall_64+0x35/0x80<br /> entry_SYSCALL_64_after_hwframe+0x46/0xb0

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> media: xilinx: vipp: Fix refcount leak in xvip_graph_dma_init<br /> <br /> of_get_child_by_name() 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.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ASoC: qcom: Add checks for devm_kcalloc<br /> <br /> As the devm_kcalloc may return NULL, the return value needs to be checked<br /> to avoid NULL poineter dereference.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> s390/cio: fix out-of-bounds access on cio_ignore free<br /> <br /> The channel-subsystem-driver scans for newly available devices whenever<br /> device-IDs are removed from the cio_ignore list using a command such as:<br /> <br /> echo free &gt;/proc/cio_ignore<br /> <br /> Since an I/O device scan might interfer with running I/Os, commit<br /> 172da89ed0ea ("s390/cio: avoid excessive path-verification requests")<br /> introduced an optimization to exclude online devices from the scan.<br /> <br /> The newly added check for online devices incorrectly assumes that<br /> an I/O-subchannel&amp;#39;s drvdata points to a struct io_subchannel_private.<br /> For devices that are bound to a non-default I/O subchannel driver, such<br /> as the vfio_ccw driver, this results in an out-of-bounds read access<br /> during each scan.<br /> <br /> Fix this by changing the scan logic to rely on a driver-independent<br /> online indication. For this we can use struct subchannel-&gt;config.ena,<br /> which is the driver&amp;#39;s requested subchannel-enabled state. Since I/Os<br /> can only be started on enabled subchannels, this matches the intent<br /> of the original optimization of not scanning devices where I/O might<br /> be running.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ext4: fix potential out of bound read in ext4_fc_replay_scan()<br /> <br /> For scan loop must ensure that at least EXT4_FC_TAG_BASE_LEN space. If remain<br /> space less than EXT4_FC_TAG_BASE_LEN which will lead to out of bound read<br /> when mounting corrupt file system image.<br /> ADD_RANGE/HEAD/TAIL is needed to add extra check when do journal scan, as this<br /> three tags will read data during scan, tag length couldn&amp;#39;t less than data length<br /> which will read.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ASoC: sof_es8336: fix possible use-after-free in sof_es8336_remove()<br /> <br /> sof_es8336_remove() calls cancel_delayed_work(). However, that<br /> function does not wait until the work function finishes. This<br /> means that the callback function may still be running after<br /> the driver&amp;#39;s remove function has finished, which would result<br /> in a use-after-free.<br /> <br /> Fix by calling cancel_delayed_work_sync(), which ensures that<br /> the work is properly cancelled, no longer running, and unable<br /> to re-schedule itself.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> mtd: core: fix possible resource leak in init_mtd()<br /> <br /> I got the error report while inject fault in init_mtd():<br /> <br /> sysfs: cannot create duplicate filename &amp;#39;/devices/virtual/bdi/mtd-0&amp;#39;<br /> Call Trace:<br /> <br /> dump_stack_lvl+0x67/0x83<br /> sysfs_warn_dup+0x60/0x70<br /> sysfs_create_dir_ns+0x109/0x120<br /> kobject_add_internal+0xce/0x2f0<br /> kobject_add+0x98/0x110<br /> device_add+0x179/0xc00<br /> device_create_groups_vargs+0xf4/0x100<br /> device_create+0x7b/0xb0<br /> bdi_register_va.part.13+0x58/0x2d0<br /> bdi_register+0x9b/0xb0<br /> init_mtd+0x62/0x171 [mtd]<br /> do_one_initcall+0x6c/0x3c0<br /> do_init_module+0x58/0x222<br /> load_module+0x268e/0x27d0<br /> __do_sys_finit_module+0xd5/0x140<br /> do_syscall_64+0x37/0x90<br /> entry_SYSCALL_64_after_hwframe+0x63/0xcd<br /> <br /> kobject_add_internal failed for mtd-0 with -EEXIST, don&amp;#39;t try to register<br /> things with the same name in the same directory.<br /> Error registering mtd class or bdi: -17<br /> <br /> If init_mtdchar() fails in init_mtd(), mtd_bdi will not be unregistered,<br /> as a result, we can&amp;#39;t load the mtd module again, to fix this by calling<br /> bdi_unregister(mtd_bdi) after out_procfs label.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amdkfd: Fix double release compute pasid<br /> <br /> If kfd_process_device_init_vm returns failure after vm is converted to<br /> compute vm and vm-&gt;pasid set to compute pasid, KFD will not take<br /> pdd-&gt;drm_file reference. As a result, drm close file handler maybe<br /> called to release the compute pasid before KFD process destroy worker to<br /> release the same pasid and set vm-&gt;pasid to zero, this generates below<br /> WARNING backtrace and NULL pointer access.<br /> <br /> Add helper amdgpu_amdkfd_gpuvm_set_vm_pasid and call it at the last step<br /> of kfd_process_device_init_vm, to ensure vm pasid is the original pasid<br /> if acquiring vm failed or is the compute pasid with pdd-&gt;drm_file<br /> reference taken to avoid double release same pasid.<br /> <br /> amdgpu: Failed to create process VM object<br /> ida_free called for id=32770 which is not allocated.<br /> WARNING: CPU: 57 PID: 72542 at ../lib/idr.c:522 ida_free+0x96/0x140<br /> RIP: 0010:ida_free+0x96/0x140<br /> Call Trace:<br /> amdgpu_pasid_free_delayed+0xe1/0x2a0 [amdgpu]<br /> amdgpu_driver_postclose_kms+0x2d8/0x340 [amdgpu]<br /> drm_file_free.part.13+0x216/0x270 [drm]<br /> drm_close_helper.isra.14+0x60/0x70 [drm]<br /> drm_release+0x6e/0xf0 [drm]<br /> __fput+0xcc/0x280<br /> ____fput+0xe/0x20<br /> task_work_run+0x96/0xc0<br /> do_exit+0x3d0/0xc10<br /> <br /> BUG: kernel NULL pointer dereference, address: 0000000000000000<br /> RIP: 0010:ida_free+0x76/0x140<br /> Call Trace:<br /> amdgpu_pasid_free_delayed+0xe1/0x2a0 [amdgpu]<br /> amdgpu_driver_postclose_kms+0x2d8/0x340 [amdgpu]<br /> drm_file_free.part.13+0x216/0x270 [drm]<br /> drm_close_helper.isra.14+0x60/0x70 [drm]<br /> drm_release+0x6e/0xf0 [drm]<br /> __fput+0xcc/0x280<br /> ____fput+0xe/0x20<br /> task_work_run+0x96/0xc0<br /> do_exit+0x3d0/0xc10

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> lockd: set other missing fields when unlocking files<br /> <br /> vfs_lock_file() expects the struct file_lock to be fully initialised by<br /> the caller. Re-exported NFSv3 has been seen to Oops if the fl_file field<br /> is NULL.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> iommu/omap: Fix buffer overflow in debugfs<br /> <br /> There are two issues here:<br /> <br /> 1) The "len" variable needs to be checked before the very first write.<br /> Otherwise if omap2_iommu_dump_ctx() with "bytes" less than 32 it is a<br /> buffer overflow.<br /> 2) The snprintf() function returns the number of bytes that *would* have<br /> been copied if there were enough space. But we want to know the<br /> number of bytes which were *actually* copied so use scnprintf()<br /> instead.