Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> dmaengine: dw-edma: HDMA: Add sync read before starting the DMA transfer in remote setup<br /> <br /> The Linked list element and pointer are not stored in the same memory as<br /> the HDMA controller register. If the doorbell register is toggled before<br /> the full write of the linked list a race condition error will occur.<br /> In remote setup we can only use a readl to the memory to assure the full<br /> write has occurred.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/nouveau: keep DMA buffers required for suspend/resume<br /> <br /> Nouveau deallocates a few buffers post GPU init which are required for GPU suspend/resume to function correctly.<br /> This is likely not as big an issue on systems where the NVGPU is the only GPU, but on multi-GPU set ups it leads to a regression where the kernel module errors and results in a system-wide rendering freeze.<br /> <br /> This commit addresses that regression by moving the two buffers required for suspend and resume to be deallocated at driver unload instead of post init.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> fs/ntfs3: Fixed overflow check in mi_enum_attr()

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: nl80211: reject iftype change with mesh ID change<br /> <br /> It&amp;#39;s currently possible to change the mesh ID when the<br /> interface isn&amp;#39;t yet in mesh mode, at the same time as<br /> changing it into mesh mode. This leads to an overwrite<br /> of data in the wdev-&gt;u union for the interface type it<br /> currently has, causing cfg80211_change_iface() to do<br /> wrong things when switching.<br /> <br /> We could probably allow setting an interface to mesh<br /> while setting the mesh ID at the same time by doing a<br /> different order of operations here, but realistically<br /> there&amp;#39;s no userspace that&amp;#39;s going to do this, so just<br /> disallow changes in iftype when setting mesh ID.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> netfilter: nft_flow_offload: reset dst in route object after setting up flow<br /> <br /> dst is transferred to the flow object, route object does not own it<br /> anymore. Reset dst in route object, otherwise if flow_offload_add()<br /> fails, error path releases dst twice, leading to a refcount underflow.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> mptcp: fix data races on remote_id<br /> <br /> Similar to the previous patch, address the data race on<br /> remote_id, adding the suitable ONCE annotations.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> usb: gadget: ncm: Avoid dropping datagrams of properly parsed NTBs<br /> <br /> It is observed sometimes when tethering is used over NCM with Windows 11<br /> as host, at some instances, the gadget_giveback has one byte appended at<br /> the end of a proper NTB. When the NTB is parsed, unwrap call looks for<br /> any leftover bytes in SKB provided by u_ether and if there are any pending<br /> bytes, it treats them as a separate NTB and parses it. But in case the<br /> second NTB (as per unwrap call) is faulty/corrupt, all the datagrams that<br /> were parsed properly in the first NTB and saved in rx_list are dropped.<br /> <br /> Adding a few custom traces showed the following:<br /> [002] d..1 7828.532866: dwc3_gadget_giveback: ep1out:<br /> req 000000003868811a length 1025/16384 zsI ==&gt; 0<br /> [002] d..1 7828.532867: ncm_unwrap_ntb: K: ncm_unwrap_ntb toprocess: 1025<br /> [002] d..1 7828.532867: ncm_unwrap_ntb: K: ncm_unwrap_ntb nth: 1751999342<br /> [002] d..1 7828.532868: ncm_unwrap_ntb: K: ncm_unwrap_ntb seq: 0xce67<br /> [002] d..1 7828.532868: ncm_unwrap_ntb: K: ncm_unwrap_ntb blk_len: 0x400<br /> [002] d..1 7828.532868: ncm_unwrap_ntb: K: ncm_unwrap_ntb ndp_len: 0x10<br /> [002] d..1 7828.532869: ncm_unwrap_ntb: K: Parsed NTB with 1 frames<br /> <br /> In this case, the giveback is of 1025 bytes and block length is 1024.<br /> The rest 1 byte (which is 0x00) won&amp;#39;t be parsed resulting in drop of<br /> all datagrams in rx_list.<br /> <br /> Same is case with packets of size 2048:<br /> [002] d..1 7828.557948: dwc3_gadget_giveback: ep1out:<br /> req 0000000011dfd96e length 2049/16384 zsI ==&gt; 0<br /> [002] d..1 7828.557949: ncm_unwrap_ntb: K: ncm_unwrap_ntb nth: 1751999342<br /> [002] d..1 7828.557950: ncm_unwrap_ntb: K: ncm_unwrap_ntb blk_len: 0x800<br /> <br /> Lecroy shows one byte coming in extra confirming that the byte is coming<br /> in from PC:<br /> <br /> Transfer 2959 - Bytes Transferred(1025) Timestamp((18.524 843 590)<br /> - Transaction 8391 - Data(1025 bytes) Timestamp(18.524 843 590)<br /> --- Packet 4063861<br /> Data(1024 bytes)<br /> Duration(2.117us) Idle(14.700ns) Timestamp(18.524 843 590)<br /> --- Packet 4063863<br /> Data(1 byte)<br /> Duration(66.160ns) Time(282.000ns) Timestamp(18.524 845 722)<br /> <br /> According to Windows driver, no ZLP is needed if wBlockLength is non-zero,<br /> because the non-zero wBlockLength has already told the function side the<br /> size of transfer to be expected. However, there are in-market NCM devices<br /> that rely on ZLP as long as the wBlockLength is multiple of wMaxPacketSize.<br /> To deal with such devices, it pads an extra 0 at end so the transfer is no<br /> longer multiple of wMaxPacketSize.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> lib/Kconfig.debug: TEST_IOV_ITER depends on MMU<br /> <br /> Trying to run the iov_iter unit test on a nommu system such as the qemu<br /> kc705-nommu emulation results in a crash.<br /> <br /> KTAP version 1<br /> # Subtest: iov_iter<br /> # module: kunit_iov_iter<br /> 1..9<br /> BUG: failure at mm/nommu.c:318/vmap()!<br /> Kernel panic - not syncing: BUG!<br /> <br /> The test calls vmap() directly, but vmap() is not supported on nommu<br /> systems, causing the crash. TEST_IOV_ITER therefore needs to depend on<br /> MMU.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> Revert "drm/amd/pm: resolve reboot exception for si oland"<br /> <br /> This reverts commit e490d60a2f76bff636c68ce4fe34c1b6c34bbd86.<br /> <br /> This causes hangs on SI when DC is enabled and errors on driver<br /> reboot and power off cycles.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> phonet/pep: fix racy skb_queue_empty() use<br /> <br /> The receive queues are protected by their respective spin-lock, not<br /> the socket lock. This could lead to skb_peek() unexpectedly<br /> returning NULL or a pointer to an already dequeued socket buffer.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> Revert "net/mlx5: Block entering switchdev mode with ns inconsistency"<br /> <br /> This reverts commit 662404b24a4c4d839839ed25e3097571f5938b9b.<br /> The revert is required due to the suspicion it is not good for anything<br /> and cause crash.

Missing Authorization vulnerability in Flothemes Flo Forms.This issue affects Flo Forms: from n/a through 1.0.42.