Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/i915: mark requests for GuC virtual engines to avoid use-after-free<br /> <br /> References to i915_requests may be trapped by userspace inside a<br /> sync_file or dmabuf (dma-resv) and held indefinitely across different<br /> proceses. To counter-act the memory leaks, we try to not to keep<br /> references from the request past their completion.<br /> On the other side on fence release we need to know if rq-&gt;engine<br /> is valid and points to hw engine (true for non-virtual requests).<br /> To make it possible extra bit has been added to rq-&gt;execution_mask,<br /> for marking virtual engines.<br /> <br /> (cherry picked from commit 280410677af763f3871b93e794a199cfcf6fb580)

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> usb: gadget: u_serial: Add null pointer check in gserial_resume<br /> <br /> Consider a case where gserial_disconnect has already cleared<br /> gser-&gt;ioport. And if a wakeup interrupt triggers afterwards,<br /> gserial_resume gets called, which will lead to accessing of<br /> gser-&gt;ioport and thus causing null pointer dereference.Add<br /> a null pointer check to prevent this.<br /> <br /> Added a static spinlock to prevent gser-&gt;ioport from becoming<br /> null after the newly added check.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> cpufreq: amd-pstate: fix global sysfs attribute type<br /> <br /> In commit 3666062b87ec ("cpufreq: amd-pstate: move to use bus_get_dev_root()")<br /> the "amd_pstate" attributes where moved from a dedicated kobject to the<br /> cpu root kobject.<br /> <br /> While the dedicated kobject expects to contain kobj_attributes the root<br /> kobject needs device_attributes.<br /> <br /> As the changed arguments are not used by the callbacks it works most of<br /> the time.<br /> However CFI will detect this issue:<br /> <br /> [ 4947.849350] CFI failure at dev_attr_show+0x24/0x60 (target: show_status+0x0/0x70; expected type: 0x8651b1de)<br /> ...<br /> [ 4947.849409] Call Trace:<br /> [ 4947.849410] <br /> [ 4947.849411] ? __warn+0xcf/0x1c0<br /> [ 4947.849414] ? dev_attr_show+0x24/0x60<br /> [ 4947.849415] ? report_cfi_failure+0x4e/0x60<br /> [ 4947.849417] ? handle_cfi_failure+0x14c/0x1d0<br /> [ 4947.849419] ? __cfi_show_status+0x10/0x10<br /> [ 4947.849420] ? handle_bug+0x4f/0x90<br /> [ 4947.849421] ? exc_invalid_op+0x1a/0x60<br /> [ 4947.849422] ? asm_exc_invalid_op+0x1a/0x20<br /> [ 4947.849424] ? __cfi_show_status+0x10/0x10<br /> [ 4947.849425] ? dev_attr_show+0x24/0x60<br /> [ 4947.849426] sysfs_kf_seq_show+0xa6/0x110<br /> [ 4947.849433] seq_read_iter+0x16c/0x4b0<br /> [ 4947.849436] vfs_read+0x272/0x2d0<br /> [ 4947.849438] ksys_read+0x72/0xe0<br /> [ 4947.849439] do_syscall_64+0x76/0xb0<br /> [ 4947.849440] ? do_user_addr_fault+0x252/0x650<br /> [ 4947.849442] ? exc_page_fault+0x7a/0x1b0<br /> [ 4947.849443] entry_SYSCALL_64_after_hwframe+0x72/0xdc

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net/mlx5: DR, fix memory leak in mlx5dr_cmd_create_reformat_ctx<br /> <br /> when mlx5_cmd_exec failed in mlx5dr_cmd_create_reformat_ctx, the memory<br /> pointed by &amp;#39;in&amp;#39; is not released, which will cause memory leak. Move memory<br /> release after mlx5_cmd_exec.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ARM: dts: exynos: Use Exynos5420 compatible for the MIPI video phy<br /> <br /> For some reason, the driver adding support for Exynos5420 MIPI phy<br /> back in 2016 wasn&amp;#39;t used on Exynos5420, which caused a kernel panic.<br /> Add the proper compatible for it.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> mtd: rawnand: brcmnand: Fix potential out-of-bounds access in oob write<br /> <br /> When the oob buffer length is not in multiple of words, the oob write<br /> function does out-of-bounds read on the oob source buffer at the last<br /> iteration. Fix that by always checking length limit on the oob buffer<br /> read and fill with 0xff when reaching the end of the buffer to the oob<br /> registers.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: cfg80211: reject auth/assoc to AP with our address<br /> <br /> If the AP uses our own address as its MLD address or BSSID, then<br /> clearly something&amp;#39;s wrong. Reject such connections so we don&amp;#39;t<br /> try and fail later.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amdgpu: Fix sdma v4 sw fini error<br /> <br /> Fix sdma v4 sw fini error for sdma 4.2.2 to<br /> solve the following general protection fault<br /> <br /> [ +0.108196] general protection fault, probably for non-canonical<br /> address 0xd5e5a4ae79d24a32: 0000 [#1] PREEMPT SMP PTI<br /> [ +0.000018] RIP: 0010:free_fw_priv+0xd/0x70<br /> [ +0.000022] Call Trace:<br /> [ +0.000012] <br /> [ +0.000011] release_firmware+0x55/0x80<br /> [ +0.000021] amdgpu_ucode_release+0x11/0x20 [amdgpu]<br /> [ +0.000415] amdgpu_sdma_destroy_inst_ctx+0x4f/0x90 [amdgpu]<br /> [ +0.000360] sdma_v4_0_sw_fini+0xce/0x110 [amdgpu]

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amdgpu: unmap and remove csa_va properly<br /> <br /> Root PD BO should be reserved before unmap and remove<br /> a bo_va from VM otherwise lockdep will complain.<br /> <br /> v2: check fpriv-&gt;csa_va is not NULL instead of amdgpu_mcbp (christian)<br /> <br /> [14616.936827] WARNING: CPU: 6 PID: 1711 at drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c:1762 amdgpu_vm_bo_del+0x399/0x3f0 [amdgpu]<br /> [14616.937096] Call Trace:<br /> [14616.937097] <br /> [14616.937102] amdgpu_driver_postclose_kms+0x249/0x2f0 [amdgpu]<br /> [14616.937187] drm_file_free+0x1d6/0x300 [drm]<br /> [14616.937207] drm_close_helper.isra.0+0x62/0x70 [drm]<br /> [14616.937220] drm_release+0x5e/0x100 [drm]<br /> [14616.937234] __fput+0x9f/0x280<br /> [14616.937239] ____fput+0xe/0x20<br /> [14616.937241] task_work_run+0x61/0x90<br /> [14616.937246] exit_to_user_mode_prepare+0x215/0x220<br /> [14616.937251] syscall_exit_to_user_mode+0x2a/0x60<br /> [14616.937254] do_syscall_64+0x48/0x90<br /> [14616.937257] entry_SYSCALL_64_after_hwframe+0x63/0xcd

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> cpufreq: davinci: Fix clk use after free<br /> <br /> The remove function first frees the clks and only then calls<br /> cpufreq_unregister_driver(). If one of the cpufreq callbacks is called<br /> just before cpufreq_unregister_driver() is run, the freed clks might be<br /> used.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> vdpa: Add max vqp attr to vdpa_nl_policy for nlattr length check<br /> <br /> The vdpa_nl_policy structure is used to validate the nlattr when parsing<br /> the incoming nlmsg. It will ensure the attribute being described produces<br /> a valid nlattr pointer in info-&gt;attrs before entering into each handler<br /> in vdpa_nl_ops.<br /> <br /> That is to say, the missing part in vdpa_nl_policy may lead to illegal<br /> nlattr after parsing, which could lead to OOB read just like CVE-2023-3773.<br /> <br /> This patch adds the missing nla_policy for vdpa max vqp attr to avoid<br /> such bugs.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: mt76: mt76x0: fix oob access in mt76x0_phy_get_target_power<br /> <br /> After &amp;#39;commit ba45841ca5eb ("wifi: mt76: mt76x02: simplify struct<br /> mt76x02_rate_power")&amp;#39;, mt76x02 relies on ht[0-7] rate_power data for<br /> vht mcs{0,7}, while it uses vth[0-1] rate_power for vht mcs {8,9}.<br /> Fix a possible out-of-bound access in mt76x0_phy_get_target_power routine.