Vulnerabilidades

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/bridge: megachips: Fix a null pointer dereference bug<br /> <br /> When removing the module we will get the following warning:<br /> <br /> [ 31.911505] i2c-core: driver [stdp2690-ge-b850v3-fw] unregistered<br /> [ 31.912484] general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] PREEMPT SMP KASAN PTI<br /> [ 31.913338] KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]<br /> [ 31.915280] RIP: 0010:drm_bridge_remove+0x97/0x130<br /> [ 31.921825] Call Trace:<br /> [ 31.922533] stdp4028_ge_b850v3_fw_remove+0x34/0x60 [megachips_stdpxxxx_ge_b850v3_fw]<br /> [ 31.923139] i2c_device_remove+0x181/0x1f0<br /> <br /> The two bridges (stdp2690, stdp4028) do not probe at the same time, so<br /> the driver does not call ge_b850v3_resgiter() when probing, causing the<br /> driver to try to remove the object that has not been initialized.<br /> <br /> Fix this by checking whether both the bridges are probed.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> perf/x86/intel/uncore: Fix reference count leak in hswep_has_limit_sbox()<br /> <br /> pci_get_device() will increase the reference count for the returned<br /> &amp;#39;dev&amp;#39;. We need to call pci_dev_put() to decrease the reference count.<br /> Since &amp;#39;dev&amp;#39; is only used in pci_read_config_dword(), let&amp;#39;s add<br /> pci_dev_put() right after it.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> coresight: trbe: remove cpuhp instance node before remove cpuhp state<br /> <br /> cpuhp_state_add_instance() and cpuhp_state_remove_instance() should<br /> be used in pairs. Or there will lead to the warn on<br /> cpuhp_remove_multi_state() since the cpuhp_step list is not empty.<br /> <br /> The following is the error log with &amp;#39;rmmod coresight-trbe&amp;#39;:<br /> Error: Removing state 215 which has instances left.<br /> Call trace:<br /> __cpuhp_remove_state_cpuslocked+0x144/0x160<br /> __cpuhp_remove_state+0xac/0x100<br /> arm_trbe_device_remove+0x2c/0x60 [coresight_trbe]<br /> platform_remove+0x34/0x70<br /> device_remove+0x54/0x90<br /> device_release_driver_internal+0x1e4/0x250<br /> driver_detach+0x5c/0xb0<br /> bus_remove_driver+0x64/0xc0<br /> driver_unregister+0x3c/0x70<br /> platform_driver_unregister+0x20/0x30<br /> arm_trbe_exit+0x1c/0x658 [coresight_trbe]<br /> __arm64_sys_delete_module+0x1ac/0x24c<br /> invoke_syscall+0x50/0x120<br /> el0_svc_common.constprop.0+0x58/0x1a0<br /> do_el0_svc+0x38/0xd0<br /> el0_svc+0x2c/0xc0<br /> el0t_64_sync_handler+0x1ac/0x1b0<br /> el0t_64_sync+0x19c/0x1a0<br /> ---[ end trace 0000000000000000 ]---

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ACPI: tables: FPDT: Don&amp;#39;t call acpi_os_map_memory() on invalid phys address<br /> <br /> On a Packard Bell Dot SC (Intel Atom N2600 model) there is a FPDT table<br /> which contains invalid physical addresses, with high bits set which fall<br /> outside the range of the CPU-s supported physical address range.<br /> <br /> Calling acpi_os_map_memory() on such an invalid phys address leads to<br /> the below WARN_ON in ioremap triggering resulting in an oops/stacktrace.<br /> <br /> Add code to verify the physical address before calling acpi_os_map_memory()<br /> to fix / avoid the oops.<br /> <br /> [ 1.226900] ioremap: invalid physical address 3001000000000000<br /> [ 1.226949] ------------[ cut here ]------------<br /> [ 1.226962] WARNING: CPU: 1 PID: 1 at arch/x86/mm/ioremap.c:200 __ioremap_caller.cold+0x43/0x5f<br /> [ 1.226996] Modules linked in:<br /> [ 1.227016] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 6.0.0-rc3+ #490<br /> [ 1.227029] Hardware name: Packard Bell dot s/SJE01_CT, BIOS V1.10 07/23/2013<br /> [ 1.227038] RIP: 0010:__ioremap_caller.cold+0x43/0x5f<br /> [ 1.227054] Code: 96 00 00 e9 f8 af 24 ff 89 c6 48 c7 c7 d8 0c 84 99 e8 6a 96 00 00 e9 76 af 24 ff 48 89 fe 48 c7 c7 a8 0c 84 99 e8 56 96 00 00 0b e9 60 af 24 ff 48 8b 34 24 48 c7 c7 40 0d 84 99 e8 3f 96 00<br /> [ 1.227067] RSP: 0000:ffffb18c40033d60 EFLAGS: 00010286<br /> [ 1.227084] RAX: 0000000000000032 RBX: 3001000000000000 RCX: 0000000000000000<br /> [ 1.227095] RDX: 0000000000000001 RSI: 00000000ffffdfff RDI: 00000000ffffffff<br /> [ 1.227105] RBP: 3001000000000000 R08: 0000000000000000 R09: ffffb18c40033c18<br /> [ 1.227115] R10: 0000000000000003 R11: ffffffff99d62fe8 R12: 0000000000000008<br /> [ 1.227124] R13: 0003001000000000 R14: 0000000000001000 R15: 3001000000000000<br /> [ 1.227135] FS: 0000000000000000(0000) GS:ffff913a3c080000(0000) knlGS:0000000000000000<br /> [ 1.227146] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> [ 1.227156] CR2: 0000000000000000 CR3: 0000000018c26000 CR4: 00000000000006e0<br /> [ 1.227167] Call Trace:<br /> [ 1.227176] <br /> [ 1.227185] ? acpi_os_map_iomem+0x1c9/0x1e0<br /> [ 1.227215] ? kmem_cache_alloc_trace+0x187/0x370<br /> [ 1.227254] acpi_os_map_iomem+0x1c9/0x1e0<br /> [ 1.227288] acpi_init_fpdt+0xa8/0x253<br /> [ 1.227308] ? acpi_debugfs_init+0x1f/0x1f<br /> [ 1.227339] do_one_initcall+0x5a/0x300<br /> [ 1.227406] ? rcu_read_lock_sched_held+0x3f/0x80<br /> [ 1.227442] kernel_init_freeable+0x28b/0x2cc<br /> [ 1.227512] ? rest_init+0x170/0x170<br /> [ 1.227538] kernel_init+0x16/0x140<br /> [ 1.227552] ret_from_fork+0x1f/0x30<br /> [ 1.227639] <br /> [ 1.227647] irq event stamp: 186819<br /> [ 1.227656] hardirqs last enabled at (186825): [] __up_console_sem+0x5e/0x70<br /> [ 1.227672] hardirqs last disabled at (186830): [] __up_console_sem+0x43/0x70<br /> [ 1.227686] softirqs last enabled at (186576): [] __irq_exit_rcu+0xed/0x160<br /> [ 1.227701] softirqs last disabled at (186569): [] __irq_exit_rcu+0xed/0x160<br /> [ 1.227715] ---[ end trace 0000000000000000 ]---

*** 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 /> 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 /> 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 /> 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 /> 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 /> 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 /> 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 /> drivers: serial: jsm: fix some leaks in probe<br /> <br /> This error path needs to unwind instead of just returning directly.