Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> pci_iounmap(): Fix MMIO mapping leak<br /> <br /> The #ifdef ARCH_HAS_GENERIC_IOPORT_MAP accidentally also guards iounmap(),<br /> which means MMIO mappings are leaked.<br /> <br /> Move the guard so we call iounmap() for MMIO mappings.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> crypto: qat - resolve race condition during AER recovery<br /> <br /> During the PCI AER system&amp;#39;s error recovery process, the kernel driver<br /> may encounter a race condition with freeing the reset_data structure&amp;#39;s<br /> memory. If the device restart will take more than 10 seconds the function<br /> scheduling that restart will exit due to a timeout, and the reset_data<br /> structure will be freed. However, this data structure is used for<br /> completion notification after the restart is completed, which leads<br /> to a UAF bug.<br /> <br /> This results in a KFENCE bug notice.<br /> <br /> BUG: KFENCE: use-after-free read in adf_device_reset_worker+0x38/0xa0 [intel_qat]<br /> Use-after-free read at 0x00000000bc56fddf (in kfence-#142):<br /> adf_device_reset_worker+0x38/0xa0 [intel_qat]<br /> process_one_work+0x173/0x340<br /> <br /> To resolve this race condition, the memory associated to the container<br /> of the work_struct is freed on the worker if the timeout expired,<br /> otherwise on the function that schedules the worker.<br /> The timeout detection can be done by checking if the caller is<br /> still waiting for completion or not by using completion_done() function.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> KVM: Always flush async #PF workqueue when vCPU is being destroyed<br /> <br /> Always flush the per-vCPU async #PF workqueue when a vCPU is clearing its<br /> completion queue, e.g. when a VM and all its vCPUs is being destroyed.<br /> KVM must ensure that none of its workqueue callbacks is running when the<br /> last reference to the KVM _module_ is put. Gifting a reference to the<br /> associated VM prevents the workqueue callback from dereferencing freed<br /> vCPU/VM memory, but does not prevent the KVM module from being unloaded<br /> before the callback completes.<br /> <br /> Drop the misguided VM refcount gifting, as calling kvm_put_kvm() from<br /> async_pf_execute() if kvm_put_kvm() flushes the async #PF workqueue will<br /> result in deadlock. async_pf_execute() can&amp;#39;t return until kvm_put_kvm()<br /> finishes, and kvm_put_kvm() can&amp;#39;t return until async_pf_execute() finishes:<br /> <br /> WARNING: CPU: 8 PID: 251 at virt/kvm/kvm_main.c:1435 kvm_put_kvm+0x2d/0x320 [kvm]<br /> Modules linked in: vhost_net vhost vhost_iotlb tap kvm_intel kvm irqbypass<br /> CPU: 8 PID: 251 Comm: kworker/8:1 Tainted: G W 6.6.0-rc1-e7af8d17224a-x86/gmem-vm #119<br /> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015<br /> Workqueue: events async_pf_execute [kvm]<br /> RIP: 0010:kvm_put_kvm+0x2d/0x320 [kvm]<br /> Call Trace:<br /> <br /> async_pf_execute+0x198/0x260 [kvm]<br /> process_one_work+0x145/0x2d0<br /> worker_thread+0x27e/0x3a0<br /> kthread+0xba/0xe0<br /> ret_from_fork+0x2d/0x50<br /> ret_from_fork_asm+0x11/0x20<br /> <br /> ---[ end trace 0000000000000000 ]---<br /> INFO: task kworker/8:1:251 blocked for more than 120 seconds.<br /> Tainted: G W 6.6.0-rc1-e7af8d17224a-x86/gmem-vm #119<br /> "echo 0 &gt; /proc/sys/kernel/hung_task_timeout_secs" disables this message.<br /> task:kworker/8:1 state:D stack:0 pid:251 ppid:2 flags:0x00004000<br /> Workqueue: events async_pf_execute [kvm]<br /> Call Trace:<br /> <br /> __schedule+0x33f/0xa40<br /> schedule+0x53/0xc0<br /> schedule_timeout+0x12a/0x140<br /> __wait_for_common+0x8d/0x1d0<br /> __flush_work.isra.0+0x19f/0x2c0<br /> kvm_clear_async_pf_completion_queue+0x129/0x190 [kvm]<br /> kvm_arch_destroy_vm+0x78/0x1b0 [kvm]<br /> kvm_put_kvm+0x1c1/0x320 [kvm]<br /> async_pf_execute+0x198/0x260 [kvm]<br /> process_one_work+0x145/0x2d0<br /> worker_thread+0x27e/0x3a0<br /> kthread+0xba/0xe0<br /> ret_from_fork+0x2d/0x50<br /> ret_from_fork_asm+0x11/0x20<br /> <br /> <br /> If kvm_clear_async_pf_completion_queue() actually flushes the workqueue,<br /> then there&amp;#39;s no need to gift async_pf_execute() a reference because all<br /> invocations of async_pf_execute() will be forced to complete before the<br /> vCPU and its VM are destroyed/freed. And that in turn fixes the module<br /> unloading bug as __fput() won&amp;#39;t do module_put() on the last vCPU reference<br /> until the vCPU has been freed, e.g. if closing the vCPU file also puts the<br /> last reference to the KVM module.<br /> <br /> Note that kvm_check_async_pf_completion() may also take the work item off<br /> the completion queue and so also needs to flush the work queue, as the<br /> work will not be seen by kvm_clear_async_pf_completion_queue(). Waiting<br /> on the workqueue could theoretically delay a vCPU due to waiting for the<br /> work to complete, but that&amp;#39;s a very, very small chance, and likely a very<br /> small delay. kvm_arch_async_page_present_queued() unconditionally makes a<br /> new request, i.e. will effectively delay entering the guest, so the<br /> remaining work is really just:<br /> <br /> trace_kvm_async_pf_completed(addr, cr2_or_gpa);<br /> <br /> __kvm_vcpu_wake_up(vcpu);<br /> <br /> mmput(mm);<br /> <br /> and mmput() can&amp;#39;t drop the last reference to the page tables if the vCPU is<br /> still alive, i.e. the vCPU won&amp;#39;t get stuck tearing down page tables.<br /> <br /> Add a helper to do the flushing, specifically to deal with "wakeup all"<br /> work items, as they aren&amp;#39;t actually work items, i.e. are never placed in a<br /> workqueue. Trying to flush a bogus workqueue entry rightly makes<br /> __flush_work() complain (kudos to whoever added that sanity check).<br /> <br /> Note, commit 5f6de5cbebee ("KVM: Prevent module exit until al<br /> ---truncated---

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> clk: qcom: gcc-ipq6018: fix terminating of frequency table arrays<br /> <br /> The frequency table arrays are supposed to be terminated with an<br /> empty element. Add such entry to the end of the arrays where it<br /> is missing in order to avoid possible out-of-bound access when<br /> the table is traversed by functions like qcom_find_freq() or<br /> qcom_find_freq_floor().<br /> <br /> Only compile tested.

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> fat: fix uninitialized field in nostale filehandles<br /> <br /> When fat_encode_fh_nostale() encodes file handle without a parent it<br /> stores only first 10 bytes of the file handle. However the length of the<br /> file handle must be a multiple of 4 so the file handle is actually 12<br /> bytes long and the last two bytes remain uninitialized. This is not<br /> great at we potentially leak uninitialized information with the handle<br /> to userspace. Properly initialize the full handle length.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> clk: qcom: camcc-sc8280xp: fix terminating of frequency table arrays<br /> <br /> The frequency table arrays are supposed to be terminated with an<br /> empty element. Add such entry to the end of the arrays where it<br /> is missing in order to avoid possible out-of-bound access when<br /> the table is traversed by functions like qcom_find_freq() or<br /> qcom_find_freq_floor().<br /> <br /> Only compile tested.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> clk: qcom: gcc-ipq9574: fix terminating of frequency table arrays<br /> <br /> The frequency table arrays are supposed to be terminated with an<br /> empty element. Add such entry to the end of the arrays where it<br /> is missing in order to avoid possible out-of-bound access when<br /> the table is traversed by functions like qcom_find_freq() or<br /> qcom_find_freq_floor().<br /> <br /> Only compile tested.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> clk: qcom: gcc-ipq8074: fix terminating of frequency table arrays<br /> <br /> The frequency table arrays are supposed to be terminated with an<br /> empty element. Add such entry to the end of the arrays where it<br /> is missing in order to avoid possible out-of-bound access when<br /> the table is traversed by functions like qcom_find_freq() or<br /> qcom_find_freq_floor().<br /> <br /> Only compile tested.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> clk: qcom: gcc-ipq5018: fix terminating of frequency table arrays<br /> <br /> The frequency table arrays are supposed to be terminated with an<br /> empty element. Add such entry to the end of the arrays where it<br /> is missing in order to avoid possible out-of-bound access when<br /> the table is traversed by functions like qcom_find_freq() or<br /> qcom_find_freq_floor().

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> Bluetooth: btnxpuart: Fix btnxpuart_close<br /> <br /> Fix scheduling while atomic BUG in btnxpuart_close(), properly<br /> purge the transmit queue and free the receive skb.<br /> <br /> [ 10.973809] BUG: scheduling while atomic: kworker/u9:0/80/0x00000002<br /> ...<br /> [ 10.980740] CPU: 3 PID: 80 Comm: kworker/u9:0 Not tainted 6.8.0-rc7-0.0.0-devel-00005-g61fdfceacf09 #1<br /> [ 10.980751] Hardware name: Toradex Verdin AM62 WB on Dahlia Board (DT)<br /> [ 10.980760] Workqueue: hci0 hci_power_off [bluetooth]<br /> [ 10.981169] Call trace:<br /> ...<br /> [ 10.981363] uart_update_mctrl+0x58/0x78<br /> [ 10.981373] uart_dtr_rts+0x104/0x114<br /> [ 10.981381] tty_port_shutdown+0xd4/0xdc<br /> [ 10.981396] tty_port_close+0x40/0xbc<br /> [ 10.981407] uart_close+0x34/0x9c<br /> [ 10.981414] ttyport_close+0x50/0x94<br /> [ 10.981430] serdev_device_close+0x40/0x50<br /> [ 10.981442] btnxpuart_close+0x24/0x98 [btnxpuart]<br /> [ 10.981469] hci_dev_close_sync+0x2d8/0x718 [bluetooth]<br /> [ 10.981728] hci_dev_do_close+0x2c/0x70 [bluetooth]<br /> [ 10.981862] hci_power_off+0x20/0x64 [bluetooth]

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> dm-raid456, md/raid456: fix a deadlock for dm-raid456 while io concurrent with reshape<br /> <br /> For raid456, if reshape is still in progress, then IO across reshape<br /> position will wait for reshape to make progress. However, for dm-raid,<br /> in following cases reshape will never make progress hence IO will hang:<br /> <br /> 1) the array is read-only;<br /> 2) MD_RECOVERY_WAIT is set;<br /> 3) MD_RECOVERY_FROZEN is set;<br /> <br /> After commit c467e97f079f ("md/raid6: use valid sector values to determine<br /> if an I/O should wait on the reshape") fix the problem that IO across<br /> reshape position doesn&amp;#39;t wait for reshape, the dm-raid test<br /> shell/lvconvert-raid-reshape.sh start to hang:<br /> <br /> [root@fedora ~]# cat /proc/979/stack<br /> [] wait_woken+0x7d/0x90<br /> [] raid5_make_request+0x929/0x1d70 [raid456]<br /> [] md_handle_request+0xc2/0x3b0 [md_mod]<br /> [] raid_map+0x2c/0x50 [dm_raid]<br /> [] __map_bio+0x251/0x380 [dm_mod]<br /> [] dm_submit_bio+0x1f0/0x760 [dm_mod]<br /> [] __submit_bio+0xc2/0x1c0<br /> [] submit_bio_noacct_nocheck+0x17f/0x450<br /> [] submit_bio_noacct+0x2bc/0x780<br /> [] submit_bio+0x70/0xc0<br /> [] mpage_readahead+0x169/0x1f0<br /> [] blkdev_readahead+0x18/0x30<br /> [] read_pages+0x7c/0x3b0<br /> [] page_cache_ra_unbounded+0x1ab/0x280<br /> [] force_page_cache_ra+0x9e/0x130<br /> [] page_cache_sync_ra+0x3b/0x110<br /> [] filemap_get_pages+0x143/0xa30<br /> [] filemap_read+0xdc/0x4b0<br /> [] blkdev_read_iter+0x75/0x200<br /> [] vfs_read+0x272/0x460<br /> [] ksys_read+0x7a/0x170<br /> [] __x64_sys_read+0x1c/0x30<br /> [] do_syscall_64+0xc6/0x230<br /> [] entry_SYSCALL_64_after_hwframe+0x6c/0x74<br /> <br /> This is because reshape can&amp;#39;t make progress.<br /> <br /> For md/raid, the problem doesn&amp;#39;t exist because register new sync_thread<br /> doesn&amp;#39;t rely on the IO to be done any more:<br /> <br /> 1) If array is read-only, it can switch to read-write by ioctl/sysfs;<br /> 2) md/raid never set MD_RECOVERY_WAIT;<br /> 3) If MD_RECOVERY_FROZEN is set, mddev_suspend() doesn&amp;#39;t hold<br /> &amp;#39;reconfig_mutex&amp;#39;, hence it can be cleared and reshape can continue by<br /> sysfs api &amp;#39;sync_action&amp;#39;.<br /> <br /> However, I&amp;#39;m not sure yet how to avoid the problem in dm-raid yet. This<br /> patch on the one hand make sure raid_message() can&amp;#39;t change<br /> sync_thread() through raid_message() after presuspend(), on the other<br /> hand detect the above 3 cases before wait for IO do be done in<br /> dm_suspend(), and let dm-raid requeue those IO.