Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> Bluetooth: btmtksdio: fix use-after-free at btmtksdio_recv_event<br /> <br /> We should not access skb buffer data anymore after hci_recv_frame was<br /> called.<br /> <br /> [ 39.634809] BUG: KASAN: use-after-free in btmtksdio_recv_event+0x1b0<br /> [ 39.634855] Read of size 1 at addr ffffff80cf28a60d by task kworker<br /> [ 39.634962] Call trace:<br /> [ 39.634974] dump_backtrace+0x0/0x3b8<br /> [ 39.634999] show_stack+0x20/0x2c<br /> [ 39.635016] dump_stack_lvl+0x60/0x78<br /> [ 39.635040] print_address_description+0x70/0x2f0<br /> [ 39.635062] kasan_report+0x154/0x194<br /> [ 39.635079] __asan_report_load1_noabort+0x44/0x50<br /> [ 39.635099] btmtksdio_recv_event+0x1b0/0x1c4<br /> [ 39.635129] btmtksdio_txrx_work+0x6cc/0xac4<br /> [ 39.635157] process_one_work+0x560/0xc5c<br /> [ 39.635177] worker_thread+0x7ec/0xcc0<br /> [ 39.635195] kthread+0x2d0/0x3d0<br /> [ 39.635215] ret_from_fork+0x10/0x20<br /> [ 39.635247] Allocated by task 0:<br /> [ 39.635260] (stack is not available)<br /> [ 39.635281] Freed by task 2392:<br /> [ 39.635295] kasan_save_stack+0x38/0x68<br /> [ 39.635319] kasan_set_track+0x28/0x3c<br /> [ 39.635338] kasan_set_free_info+0x28/0x4c<br /> [ 39.635357] ____kasan_slab_free+0x104/0x150<br /> [ 39.635374] __kasan_slab_free+0x18/0x28<br /> [ 39.635391] slab_free_freelist_hook+0x114/0x248<br /> [ 39.635410] kfree+0xf8/0x2b4<br /> [ 39.635427] skb_free_head+0x58/0x98<br /> [ 39.635447] skb_release_data+0x2f4/0x410<br /> [ 39.635464] skb_release_all+0x50/0x60<br /> [ 39.635481] kfree_skb+0xc8/0x25c<br /> [ 39.635498] hci_event_packet+0x894/0xca4 [bluetooth]<br /> [ 39.635721] hci_rx_work+0x1c8/0x68c [bluetooth]<br /> [ 39.635925] process_one_work+0x560/0xc5c<br /> [ 39.635951] worker_thread+0x7ec/0xcc0<br /> [ 39.635970] kthread+0x2d0/0x3d0<br /> [ 39.635990] ret_from_fork+0x10/0x20<br /> [ 39.636021] The buggy address belongs to the object at ffffff80cf28a600<br /> which belongs to the cache kmalloc-512 of size 512<br /> [ 39.636039] The buggy address is located 13 bytes inside of<br /> 512-byte region [ffffff80cf28a600, ffffff80cf28a800)

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> rtw89: cfo: check mac_id to avoid out-of-bounds<br /> <br /> Somehow, hardware reports incorrect mac_id and pollute memory. Check index<br /> before we access the array.<br /> <br /> UBSAN: array-index-out-of-bounds in rtw89/phy.c:2517:23<br /> index 188 is out of range for type &amp;#39;s32 [64]&amp;#39;<br /> CPU: 1 PID: 51550 Comm: irq/35-rtw89_pc Tainted: G OE<br /> Call Trace:<br /> <br /> show_stack+0x52/0x58<br /> dump_stack_lvl+0x4c/0x63<br /> dump_stack+0x10/0x12<br /> ubsan_epilogue+0x9/0x45<br /> __ubsan_handle_out_of_bounds.cold+0x44/0x49<br /> ? __alloc_skb+0x92/0x1d0<br /> rtw89_phy_cfo_parse+0x44/0x7f [rtw89_core]<br /> rtw89_core_rx+0x261/0x871 [rtw89_core]<br /> ? __alloc_skb+0xee/0x1d0<br /> rtw89_pci_napi_poll+0x3fa/0x4ea [rtw89_pci]<br /> __napi_poll+0x33/0x1a0<br /> net_rx_action+0x126/0x260<br /> ? __queue_work+0x217/0x4c0<br /> __do_softirq+0xd9/0x315<br /> ? disable_irq_nosync+0x10/0x10<br /> do_softirq.part.0+0x6d/0x90<br /> <br /> <br /> __local_bh_enable_ip+0x62/0x70<br /> rtw89_pci_interrupt_threadfn+0x182/0x1a6 [rtw89_pci]<br /> irq_thread_fn+0x28/0x60<br /> irq_thread+0xc8/0x190<br /> ? irq_thread_fn+0x60/0x60<br /> kthread+0x16b/0x190<br /> ? irq_thread_check_affinity+0xe0/0xe0<br /> ? set_kthread_struct+0x50/0x50<br /> ret_from_fork+0x22/0x30<br />

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ARM: versatile: Add missing of_node_put in dcscb_init<br /> <br /> The device_node pointer is returned by of_find_compatible_node<br /> with refcount incremented. We should use of_node_put() to avoid<br /> the refcount leak.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/msm: don&amp;#39;t free the IRQ if it was not requested<br /> <br /> As msm_drm_uninit() is called from the msm_drm_init() error path,<br /> additional care should be necessary as not to call the free_irq() for<br /> the IRQ that was not requested before (because an error occured earlier<br /> than the request_irq() call).<br /> <br /> This fixed the issue reported with the following backtrace:<br /> <br /> [ 8.571329] Trying to free already-free IRQ 187<br /> [ 8.571339] WARNING: CPU: 0 PID: 76 at kernel/irq/manage.c:1895 free_irq+0x1e0/0x35c<br /> [ 8.588746] Modules linked in: pmic_glink pdr_interface fastrpc qrtr_smd snd_soc_hdmi_codec msm fsa4480 gpu_sched drm_dp_aux_bus qrtr i2c_qcom_geni crct10dif_ce qcom_stats qcom_q6v5_pas drm_display_helper gpi qcom_pil_info drm_kms_helper qcom_q6v5 qcom_sysmon qcom_common qcom_glink_smem qcom_rng mdt_loader qmi_helpers phy_qcom_qmp ufs_qcom typec qnoc_sm8350 socinfo rmtfs_mem fuse drm ipv6<br /> [ 8.624154] CPU: 0 PID: 76 Comm: kworker/u16:2 Not tainted 5.18.0-rc5-next-20220506-00033-g6cee8cab6089-dirty #419<br /> [ 8.624161] Hardware name: Qualcomm Technologies, Inc. SM8350 HDK (DT)<br /> [ 8.641496] Workqueue: events_unbound deferred_probe_work_func<br /> [ 8.647510] pstate: 604000c5 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)<br /> [ 8.654681] pc : free_irq+0x1e0/0x35c<br /> [ 8.658454] lr : free_irq+0x1e0/0x35c<br /> [ 8.662228] sp : ffff800008ab3950<br /> [ 8.665642] x29: ffff800008ab3950 x28: 0000000000000000 x27: ffff16350f56a700<br /> [ 8.672994] x26: ffff1635025df080 x25: ffff16350251badc x24: ffff16350251bb90<br /> [ 8.680343] x23: 0000000000000000 x22: 00000000000000bb x21: ffff16350e8f9800<br /> [ 8.687690] x20: ffff16350251ba00 x19: ffff16350cbd5880 x18: ffffffffffffffff<br /> [ 8.695039] x17: 0000000000000000 x16: ffffa2dd12179434 x15: ffffa2dd1431d02d<br /> [ 8.702391] x14: 0000000000000000 x13: ffffa2dd1431d028 x12: 662d79646165726c<br /> [ 8.709740] x11: ffffa2dd13fd2438 x10: 000000000000000a x9 : 00000000000000bb<br /> [ 8.717111] x8 : ffffa2dd13fd23f0 x7 : ffff800008ab3750 x6 : 00000000fffff202<br /> [ 8.724487] x5 : ffff16377e870a18 x4 : 00000000fffff202 x3 : ffff735a6ae1b000<br /> [ 8.731851] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff1635015f8000<br /> [ 8.739217] Call trace:<br /> [ 8.741755] free_irq+0x1e0/0x35c<br /> [ 8.745198] msm_drm_uninit.isra.0+0x14c/0x294 [msm]<br /> [ 8.750548] msm_drm_bind+0x28c/0x5d0 [msm]<br /> [ 8.755081] try_to_bring_up_aggregate_device+0x164/0x1d0<br /> [ 8.760657] __component_add+0xa0/0x170<br /> [ 8.764626] component_add+0x14/0x20<br /> [ 8.768337] dp_display_probe+0x2a4/0x464 [msm]<br /> [ 8.773242] platform_probe+0x68/0xe0<br /> [ 8.777043] really_probe.part.0+0x9c/0x28c<br /> [ 8.781368] __driver_probe_device+0x98/0x144<br /> [ 8.785871] driver_probe_device+0x40/0x140<br /> [ 8.790191] __device_attach_driver+0xb4/0x120<br /> [ 8.794788] bus_for_each_drv+0x78/0xd0<br /> [ 8.798751] __device_attach+0xdc/0x184<br /> [ 8.802713] device_initial_probe+0x14/0x20<br /> [ 8.807031] bus_probe_device+0x9c/0xa4<br /> [ 8.810991] deferred_probe_work_func+0x88/0xc0<br /> [ 8.815667] process_one_work+0x1d0/0x320<br /> [ 8.819809] worker_thread+0x14c/0x444<br /> [ 8.823688] kthread+0x10c/0x110<br /> [ 8.827036] ret_from_fork+0x10/0x20<br /> <br /> Patchwork: https://patchwork.freedesktop.org/patch/485422/

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> thermal/drivers/broadcom: Fix potential NULL dereference in sr_thermal_probe<br /> <br /> platform_get_resource() may return NULL, add proper check to<br /> avoid potential NULL dereferencing.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> PM / devfreq: rk3399_dmc: Disable edev on remove()<br /> <br /> Otherwise we hit an unablanced enable-count when unbinding the DFI<br /> device:<br /> <br /> [ 1279.659119] ------------[ cut here ]------------<br /> [ 1279.659179] WARNING: CPU: 2 PID: 5638 at drivers/devfreq/devfreq-event.c:360 devfreq_event_remove_edev+0x84/0x8c<br /> ...<br /> [ 1279.659352] Hardware name: Google Kevin (DT)<br /> [ 1279.659363] pstate: 80400005 (Nzcv daif +PAN -UAO -TCO BTYPE=--)<br /> [ 1279.659371] pc : devfreq_event_remove_edev+0x84/0x8c<br /> [ 1279.659380] lr : devm_devfreq_event_release+0x1c/0x28<br /> ...<br /> [ 1279.659571] Call trace:<br /> [ 1279.659582] devfreq_event_remove_edev+0x84/0x8c<br /> [ 1279.659590] devm_devfreq_event_release+0x1c/0x28<br /> [ 1279.659602] release_nodes+0x1cc/0x244<br /> [ 1279.659611] devres_release_all+0x44/0x60<br /> [ 1279.659621] device_release_driver_internal+0x11c/0x1ac<br /> [ 1279.659629] device_driver_detach+0x20/0x2c<br /> [ 1279.659641] unbind_store+0x7c/0xb0<br /> [ 1279.659650] drv_attr_store+0x2c/0x40<br /> [ 1279.659663] sysfs_kf_write+0x44/0x58<br /> [ 1279.659672] kernfs_fop_write_iter+0xf4/0x190<br /> [ 1279.659684] vfs_write+0x2b0/0x2e4<br /> [ 1279.659693] ksys_write+0x80/0xec<br /> [ 1279.659701] __arm64_sys_write+0x24/0x30<br /> [ 1279.659714] el0_svc_common+0xf0/0x1d8<br /> [ 1279.659724] do_el0_svc_compat+0x28/0x3c<br /> [ 1279.659738] el0_svc_compat+0x10/0x1c<br /> [ 1279.659746] el0_sync_compat_handler+0xa8/0xcc<br /> [ 1279.659758] el0_sync_compat+0x188/0x1c0<br /> [ 1279.659768] ---[ end trace cec200e5094155b4 ]---

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> amt: fix memory leak for advertisement message<br /> <br /> When a gateway receives an advertisement message, it extracts relay<br /> information and then it should be freed.<br /> But the advertisement handler doesn&amp;#39;t free it.<br /> So, memory leak would occur.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/msm/a6xx: Fix refcount leak in a6xx_gpu_init<br /> <br /> of_parse_phandle() returns a node pointer with refcount<br /> incremented, we should use of_node_put() on it when not need anymore.<br /> <br /> a6xx_gmu_init() passes the node to of_find_device_by_node()<br /> and of_dma_configure(), of_find_device_by_node() will takes its<br /> reference, of_dma_configure() doesn&amp;#39;t need the node after usage.<br /> <br /> Add missing of_node_put() to avoid refcount leak.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> thermal/drivers/imx_sc_thermal: Fix refcount leak in imx_sc_thermal_probe<br /> <br /> of_find_node_by_name() returns a node pointer with refcount<br /> incremented, we should use of_node_put() on it when done.<br /> Add missing of_node_put() to avoid refcount leak.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> erofs: fix buffer copy overflow of ztailpacking feature<br /> <br /> I got some KASAN report as below:<br /> <br /> [ 46.959738] ==================================================================<br /> [ 46.960430] BUG: KASAN: use-after-free in z_erofs_shifted_transform+0x2bd/0x370<br /> [ 46.960430] Read of size 4074 at addr ffff8880300c2f8e by task fssum/188<br /> ...<br /> [ 46.960430] Call Trace:<br /> [ 46.960430] <br /> [ 46.960430] dump_stack_lvl+0x41/0x5e<br /> [ 46.960430] print_report.cold+0xb2/0x6b7<br /> [ 46.960430] ? z_erofs_shifted_transform+0x2bd/0x370<br /> [ 46.960430] kasan_report+0x8a/0x140<br /> [ 46.960430] ? z_erofs_shifted_transform+0x2bd/0x370<br /> [ 46.960430] kasan_check_range+0x14d/0x1d0<br /> [ 46.960430] memcpy+0x20/0x60<br /> [ 46.960430] z_erofs_shifted_transform+0x2bd/0x370<br /> [ 46.960430] z_erofs_decompress_pcluster+0xaae/0x1080<br /> <br /> The root cause is that the tail pcluster won&amp;#39;t be a complete filesystem<br /> block anymore. So if ztailpacking is used, the second part of an<br /> uncompressed tail pcluster may not be ``rq-&gt;pageofs_out``.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> blk-throttle: Set BIO_THROTTLED when bio has been throttled<br /> <br /> 1.In current process, all bio will set the BIO_THROTTLED flag<br /> after __blk_throtl_bio().<br /> <br /> 2.If bio needs to be throttled, it will start the timer and<br /> stop submit bio directly. Bio will submit in<br /> blk_throtl_dispatch_work_fn() when the timer expires.But in<br /> the current process, if bio is throttled. The BIO_THROTTLED<br /> will be set to bio after timer start. If the bio has been<br /> completed, it may cause use-after-free blow.<br /> <br /> BUG: KASAN: use-after-free in blk_throtl_bio+0x12f0/0x2c70<br /> Read of size 2 at addr ffff88801b8902d4 by task fio/26380<br /> <br /> dump_stack+0x9b/0xce<br /> print_address_description.constprop.6+0x3e/0x60<br /> kasan_report.cold.9+0x22/0x3a<br /> blk_throtl_bio+0x12f0/0x2c70<br /> submit_bio_checks+0x701/0x1550<br /> submit_bio_noacct+0x83/0xc80<br /> submit_bio+0xa7/0x330<br /> mpage_readahead+0x380/0x500<br /> read_pages+0x1c1/0xbf0<br /> page_cache_ra_unbounded+0x471/0x6f0<br /> do_page_cache_ra+0xda/0x110<br /> ondemand_readahead+0x442/0xae0<br /> page_cache_async_ra+0x210/0x300<br /> generic_file_buffered_read+0x4d9/0x2130<br /> generic_file_read_iter+0x315/0x490<br /> blkdev_read_iter+0x113/0x1b0<br /> aio_read+0x2ad/0x450<br /> io_submit_one+0xc8e/0x1d60<br /> __se_sys_io_submit+0x125/0x350<br /> do_syscall_64+0x2d/0x40<br /> entry_SYSCALL_64_after_hwframe+0x44/0xa9<br /> <br /> Allocated by task 26380:<br /> kasan_save_stack+0x19/0x40<br /> __kasan_kmalloc.constprop.2+0xc1/0xd0<br /> kmem_cache_alloc+0x146/0x440<br /> mempool_alloc+0x125/0x2f0<br /> bio_alloc_bioset+0x353/0x590<br /> mpage_alloc+0x3b/0x240<br /> do_mpage_readpage+0xddf/0x1ef0<br /> mpage_readahead+0x264/0x500<br /> read_pages+0x1c1/0xbf0<br /> page_cache_ra_unbounded+0x471/0x6f0<br /> do_page_cache_ra+0xda/0x110<br /> ondemand_readahead+0x442/0xae0<br /> page_cache_async_ra+0x210/0x300<br /> generic_file_buffered_read+0x4d9/0x2130<br /> generic_file_read_iter+0x315/0x490<br /> blkdev_read_iter+0x113/0x1b0<br /> aio_read+0x2ad/0x450<br /> io_submit_one+0xc8e/0x1d60<br /> __se_sys_io_submit+0x125/0x350<br /> do_syscall_64+0x2d/0x40<br /> entry_SYSCALL_64_after_hwframe+0x44/0xa9<br /> <br /> Freed by task 0:<br /> kasan_save_stack+0x19/0x40<br /> kasan_set_track+0x1c/0x30<br /> kasan_set_free_info+0x1b/0x30<br /> __kasan_slab_free+0x111/0x160<br /> kmem_cache_free+0x94/0x460<br /> mempool_free+0xd6/0x320<br /> bio_free+0xe0/0x130<br /> bio_put+0xab/0xe0<br /> bio_endio+0x3a6/0x5d0<br /> blk_update_request+0x590/0x1370<br /> scsi_end_request+0x7d/0x400<br /> scsi_io_completion+0x1aa/0xe50<br /> scsi_softirq_done+0x11b/0x240<br /> blk_mq_complete_request+0xd4/0x120<br /> scsi_mq_done+0xf0/0x200<br /> virtscsi_vq_done+0xbc/0x150<br /> vring_interrupt+0x179/0x390<br /> __handle_irq_event_percpu+0xf7/0x490<br /> handle_irq_event_percpu+0x7b/0x160<br /> handle_irq_event+0xcc/0x170<br /> handle_edge_irq+0x215/0xb20<br /> common_interrupt+0x60/0x120<br /> asm_common_interrupt+0x1e/0x40<br /> <br /> Fix this by move BIO_THROTTLED set into the queue_lock.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> regulator: scmi: Fix refcount leak in scmi_regulator_probe<br /> <br /> of_find_node_by_name() returns a node pointer with refcount<br /> incremented, we should use of_node_put() on it when done.<br /> Add missing of_node_put() to avoid refcount leak.