Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> phy: fsl-imx8mq-usb: set platform driver data<br /> <br /> Add missing platform_set_drvdata() as the data will be used in remove().

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> bnxt_en: Fix RSS context delete logic<br /> <br /> We need to free the corresponding RSS context VNIC<br /> in FW everytime an RSS context is deleted in driver.<br /> Commit 667ac333dbb7 added a check to delete the VNIC<br /> in FW only when netif_running() is true to help delete<br /> RSS contexts with interface down.<br /> <br /> Having that condition will make the driver leak VNICs<br /> in FW whenever close() happens with active RSS contexts.<br /> On the subsequent open(), as part of RSS context restoration,<br /> we will end up trying to create extra VNICs for which we<br /> did not make any reservation. FW can fail this request,<br /> thereby making us lose active RSS contexts.<br /> <br /> Suppose an RSS context is deleted already and we try to<br /> process a delete request again, then the HWRM functions<br /> will check for validity of the request and they simply<br /> return if the resource is already freed. So, even for<br /> delete-when-down cases, netif_running() check is not<br /> necessary.<br /> <br /> Remove the netif_running() condition check when deleting<br /> an RSS context.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> media: i2c/tw9906: Fix potential memory leak in tw9906_probe()<br /> <br /> In one of the error paths in tw9906_probe(), the memory allocated in<br /> v4l2_ctrl_handler_init() and v4l2_ctrl_new_std() is not freed. Fix that<br /> by calling v4l2_ctrl_handler_free() on the handler in that error path.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> media: chips-media: wave5: Fix SError of kernel panic when closed<br /> <br /> SError of kernel panic rarely happened while testing fluster.<br /> The root cause was to enter suspend mode because timeout of autosuspend<br /> delay happened.<br /> <br /> [ 48.834439] SError Interrupt on CPU0, code 0x00000000bf000000 -- SError<br /> [ 48.834455] CPU: 0 UID: 0 PID: 1067 Comm: v4l2h265dec0:sr Not tainted 6.12.9-gc9e21a1ebd75-dirty #7<br /> [ 48.834461] Hardware name: ti Texas Instruments J721S2 EVM/Texas Instruments J721S2 EVM, BIOS 2025.01-00345-gbaf3aaa8ecfa 01/01/2025<br /> [ 48.834464] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)<br /> [ 48.834468] pc : wave5_dec_clr_disp_flag+0x40/0x80 [wave5]<br /> [ 48.834488] lr : wave5_dec_clr_disp_flag+0x40/0x80 [wave5]<br /> [ 48.834495] sp : ffff8000856e3a30<br /> [ 48.834497] x29: ffff8000856e3a30 x28: ffff0008093f6010 x27: ffff000809158130<br /> [ 48.834504] x26: 0000000000000000 x25: ffff00080b625000 x24: ffff000804a9ba80<br /> [ 48.834509] x23: ffff000802343028 x22: ffff000809158150 x21: ffff000802218000<br /> [ 48.834513] x20: ffff0008093f6000 x19: ffff0008093f6000 x18: 0000000000000000<br /> [ 48.834518] x17: 0000000000000000 x16: 0000000000000000 x15: 0000ffff74009618<br /> [ 48.834523] x14: 000000010000000c x13: 0000000000000000 x12: 0000000000000000<br /> [ 48.834527] x11: ffffffffffffffff x10: ffffffffffffffff x9 : ffff000802343028<br /> [ 48.834532] x8 : ffff00080b6252a0 x7 : 0000000000000038 x6 : 0000000000000000<br /> [ 48.834536] x5 : ffff00080b625060 x4 : 0000000000000000 x3 : 0000000000000000<br /> [ 48.834541] x2 : 0000000000000000 x1 : ffff800084bf0118 x0 : ffff800084bf0000<br /> [ 48.834547] Kernel panic - not syncing: Asynchronous SError Interrupt<br /> [ 48.834549] CPU: 0 UID: 0 PID: 1067 Comm: v4l2h265dec0:sr Not tainted 6.12.9-gc9e21a1ebd75-dirty #7<br /> [ 48.834554] Hardware name: ti Texas Instruments J721S2 EVM/Texas Instruments J721S2 EVM, BIOS 2025.01-00345-gbaf3aaa8ecfa 01/01/2025<br /> [ 48.834556] Call trace:<br /> [ 48.834559] dump_backtrace+0x94/0xec<br /> [ 48.834574] show_stack+0x18/0x24<br /> [ 48.834579] dump_stack_lvl+0x38/0x90<br /> [ 48.834585] dump_stack+0x18/0x24<br /> [ 48.834588] panic+0x35c/0x3e0<br /> [ 48.834592] nmi_panic+0x40/0x8c<br /> [ 48.834595] arm64_serror_panic+0x64/0x70<br /> [ 48.834598] do_serror+0x3c/0x78<br /> [ 48.834601] el1h_64_error_handler+0x34/0x4c<br /> [ 48.834605] el1h_64_error+0x64/0x68<br /> [ 48.834608] wave5_dec_clr_disp_flag+0x40/0x80 [wave5]<br /> [ 48.834615] wave5_vpu_dec_clr_disp_flag+0x54/0x80 [wave5]<br /> [ 48.834622] wave5_vpu_dec_buf_queue+0x19c/0x1a0 [wave5]<br /> [ 48.834628] __enqueue_in_driver+0x3c/0x74 [videobuf2_common]<br /> [ 48.834639] vb2_core_qbuf+0x508/0x61c [videobuf2_common]<br /> [ 48.834646] vb2_qbuf+0xa4/0x168 [videobuf2_v4l2]<br /> [ 48.834656] v4l2_m2m_qbuf+0x80/0x238 [v4l2_mem2mem]<br /> [ 48.834666] v4l2_m2m_ioctl_qbuf+0x18/0x24 [v4l2_mem2mem]<br /> [ 48.834673] v4l_qbuf+0x48/0x5c [videodev]<br /> [ 48.834704] __video_do_ioctl+0x180/0x3f0 [videodev]<br /> [ 48.834725] video_usercopy+0x2ec/0x68c [videodev]<br /> [ 48.834745] video_ioctl2+0x18/0x24 [videodev]<br /> [ 48.834766] v4l2_ioctl+0x40/0x60 [videodev]<br /> [ 48.834786] __arm64_sys_ioctl+0xa8/0xec<br /> [ 48.834793] invoke_syscall+0x44/0x100<br /> [ 48.834800] el0_svc_common.constprop.0+0xc0/0xe0<br /> [ 48.834804] do_el0_svc+0x1c/0x28<br /> [ 48.834809] el0_svc+0x30/0xd0<br /> [ 48.834813] el0t_64_sync_handler+0xc0/0xc4<br /> [ 48.834816] el0t_64_sync+0x190/0x194<br /> [ 48.834820] SMP: stopping secondary CPUs<br /> [ 48.834831] Kernel Offset: disabled<br /> [ 48.834833] CPU features: 0x08,00002002,80200000,4200421b<br /> [ 48.834837] Memory Limit: none<br /> [ 49.161404] ---[ end Kernel panic - not syncing: Asynchronous SError Interrupt ]---

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> usb: chipidea: udc: fix DMA and SG cleanup in _ep_nuke()<br /> <br /> The ChipIdea UDC driver can encounter "not page aligned sg buffer"<br /> errors when a USB device is reconnected after being disconnected<br /> during an active transfer. This occurs because _ep_nuke() returns<br /> requests to the gadget layer without properly unmapping DMA buffers<br /> or cleaning up scatter-gather bounce buffers.<br /> <br /> Root cause:<br /> When a disconnect happens during a multi-segment DMA transfer, the<br /> request&amp;#39;s num_mapped_sgs field and sgt.sgl pointer remain set with<br /> stale values. The request is returned to the gadget driver with status<br /> -ESHUTDOWN but still has active DMA state. If the gadget driver reuses<br /> this request on reconnect without reinitializing it, the stale DMA<br /> state causes _hardware_enqueue() to skip DMA mapping (seeing non-zero<br /> num_mapped_sgs) and attempt to use freed/invalid DMA addresses,<br /> leading to alignment errors and potential memory corruption.<br /> <br /> The normal completion path via _hardware_dequeue() properly calls<br /> usb_gadget_unmap_request_by_dev() and sglist_do_debounce() before<br /> returning the request. The _ep_nuke() path must do the same cleanup<br /> to ensure requests are returned in a clean, reusable state.<br /> <br /> Fix:<br /> Add DMA unmapping and bounce buffer cleanup to _ep_nuke() to mirror<br /> the cleanup sequence in _hardware_dequeue():<br /> - Call usb_gadget_unmap_request_by_dev() if num_mapped_sgs is set<br /> - Call sglist_do_debounce() with copy=false if bounce buffer exists<br /> <br /> This ensures that when requests are returned due to endpoint shutdown,<br /> they don&amp;#39;t retain stale DMA mappings. The &amp;#39;false&amp;#39; parameter to<br /> sglist_do_debounce() prevents copying data back (appropriate for<br /> shutdown path where transfer was aborted).

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> HID: prodikeys: Check presence of pm-&gt;input_ep82<br /> <br /> Fake USB devices can send their own report descriptors for which the<br /> input_mapping() hook does not get called. In this case, pm-&gt;input_ep82 stays<br /> NULL, which leads to a crash later.<br /> <br /> This does not happen with the real device, but can be provoked by imposing as<br /> one.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> mptcp: pm: in-kernel: always set ID as avail when rm endp<br /> <br /> Syzkaller managed to find a combination of actions that was generating<br /> this warning:<br /> <br /> WARNING: net/mptcp/pm_kernel.c:1074 at __mark_subflow_endp_available net/mptcp/pm_kernel.c:1074 [inline], CPU#1: syz.7.48/2535<br /> WARNING: net/mptcp/pm_kernel.c:1074 at mptcp_pm_nl_fullmesh net/mptcp/pm_kernel.c:1446 [inline], CPU#1: syz.7.48/2535<br /> WARNING: net/mptcp/pm_kernel.c:1074 at mptcp_pm_nl_set_flags_all net/mptcp/pm_kernel.c:1474 [inline], CPU#1: syz.7.48/2535<br /> WARNING: net/mptcp/pm_kernel.c:1074 at mptcp_pm_nl_set_flags+0x5de/0x640 net/mptcp/pm_kernel.c:1538, CPU#1: syz.7.48/2535<br /> Modules linked in:<br /> CPU: 1 UID: 0 PID: 2535 Comm: syz.7.48 Not tainted 6.18.0-03987-gea5f5e676cf5 #17 PREEMPT(voluntary)<br /> Hardware name: QEMU Ubuntu 25.10 PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014<br /> RIP: 0010:__mark_subflow_endp_available net/mptcp/pm_kernel.c:1074 [inline]<br /> RIP: 0010:mptcp_pm_nl_fullmesh net/mptcp/pm_kernel.c:1446 [inline]<br /> RIP: 0010:mptcp_pm_nl_set_flags_all net/mptcp/pm_kernel.c:1474 [inline]<br /> RIP: 0010:mptcp_pm_nl_set_flags+0x5de/0x640 net/mptcp/pm_kernel.c:1538<br /> Code: 89 c7 e8 c5 8c 73 fe e9 f7 fd ff ff 49 83 ef 80 e8 b7 8c 73 fe 4c 89 ff be 03 00 00 00 e8 4a 29 e3 fe eb ac e8 a3 8c 73 fe 90 0b 90 e9 3d ff ff ff e8 95 8c 73 fe b8 a1 ff ff ff eb 1a e8 89<br /> RSP: 0018:ffffc9001535b820 EFLAGS: 00010287<br /> netdevsim0: tun_chr_ioctl cmd 1074025677<br /> RAX: ffffffff82da294d RBX: 0000000000000001 RCX: 0000000000080000<br /> RDX: ffffc900096d0000 RSI: 00000000000006d6 RDI: 00000000000006d7<br /> netdevsim0: linktype set to 823<br /> RBP: ffff88802cdb2240 R08: 00000000000104ae R09: ffffffffffffffff<br /> R10: ffffffff82da27d4 R11: 0000000000000000 R12: 0000000000000000<br /> R13: ffff88801246d8c0 R14: ffffc9001535b8b8 R15: ffff88802cdb1800<br /> FS: 00007fc6ac5a76c0(0000) GS:ffff8880f90c8000(0000) knlGS:0000000000000000<br /> netlink: &amp;#39;syz.3.50&amp;#39;: attribute type 5 has an invalid length.<br /> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> netlink: 1232 bytes leftover after parsing attributes in process `syz.3.50&amp;#39;.<br /> CR2: 0000200000010000 CR3: 0000000025b1a000 CR4: 0000000000350ef0<br /> Call Trace:<br /> <br /> mptcp_pm_set_flags net/mptcp/pm_netlink.c:277 [inline]<br /> mptcp_pm_nl_set_flags_doit+0x1d7/0x210 net/mptcp/pm_netlink.c:282<br /> genl_family_rcv_msg_doit+0x117/0x180 net/netlink/genetlink.c:1115<br /> genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]<br /> genl_rcv_msg+0x3a8/0x3f0 net/netlink/genetlink.c:1210<br /> netlink_rcv_skb+0x16d/0x240 net/netlink/af_netlink.c:2550<br /> genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219<br /> netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]<br /> netlink_unicast+0x3e9/0x4c0 net/netlink/af_netlink.c:1344<br /> netlink_sendmsg+0x4ab/0x5b0 net/netlink/af_netlink.c:1894<br /> sock_sendmsg_nosec net/socket.c:718 [inline]<br /> __sock_sendmsg+0xc9/0xf0 net/socket.c:733<br /> ____sys_sendmsg+0x272/0x3b0 net/socket.c:2608<br /> ___sys_sendmsg+0x2de/0x320 net/socket.c:2662<br /> __sys_sendmsg net/socket.c:2694 [inline]<br /> __do_sys_sendmsg net/socket.c:2699 [inline]<br /> __se_sys_sendmsg net/socket.c:2697 [inline]<br /> __x64_sys_sendmsg+0x110/0x1a0 net/socket.c:2697<br /> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]<br /> do_syscall_64+0xed/0x360 arch/x86/entry/syscall_64.c:94<br /> entry_SYSCALL_64_after_hwframe+0x77/0x7f<br /> RIP: 0033:0x7fc6adb66f6d<br /> Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48<br /> RSP: 002b:00007fc6ac5a6ff8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e<br /> RAX: ffffffffffffffda RBX: 00007fc6addf5fa0 RCX: 00007fc6adb66f6d<br /> RDX: 0000000000048084 RSI: 00002000000002c0 RDI: 000000000000000e<br /> RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000<br /> R10: 0000000000000000 R11: 0000000000000246 R12: 000000000000<br /> ---truncated---

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> vhost: move vdpa group bound check to vhost_vdpa<br /> <br /> Remove duplication by consolidating these here. This reduces the<br /> posibility of a parent driver missing them.<br /> <br /> While we&amp;#39;re at it, fix a bug in vdpa_sim where a valid ASID can be<br /> assigned to a group equal to ngroups, causing an out of bound write.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> 9p/xen: protect xen_9pfs_front_free against concurrent calls<br /> <br /> The xenwatch thread can race with other back-end change notifications<br /> and call xen_9pfs_front_free() twice, hitting the observed general<br /> protection fault due to a double-free. Guard the teardown path so only<br /> one caller can release the front-end state at a time, preventing the<br /> crash.<br /> <br /> This is a fix for the following double-free:<br /> <br /> [ 27.052347] Oops: general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b6b6b: 0000 [#1] SMP DEBUG_PAGEALLOC NOPTI<br /> [ 27.052357] CPU: 0 UID: 0 PID: 32 Comm: xenwatch Not tainted 6.18.0-02087-g51ab33fc0a8b-dirty #60 PREEMPT(none)<br /> [ 27.052363] RIP: e030:xen_9pfs_front_free+0x1d/0x150<br /> [ 27.052368] Code: 90 90 90 90 90 90 90 90 90 90 90 90 90 41 55 41 54 55 48 89 fd 48 c7 c7 48 d0 92 85 53 e8 cb cb 05 00 48 8b 45 08 48 8b 55 00 3b 28 0f 85 f9 28 35 fe 48 3b 6a 08 0f 85 ef 28 35 fe 48 89 42<br /> [ 27.052377] RSP: e02b:ffffc9004016fdd0 EFLAGS: 00010246<br /> [ 27.052381] RAX: 6b6b6b6b6b6b6b6b RBX: ffff88800d66e400 RCX: 0000000000000000<br /> [ 27.052385] RDX: 6b6b6b6b6b6b6b6b RSI: 0000000000000000 RDI: 0000000000000000<br /> [ 27.052389] RBP: ffff88800a887040 R08: 0000000000000000 R09: 0000000000000000<br /> [ 27.052393] R10: 0000000000000000 R11: 0000000000000000 R12: ffff888009e46b68<br /> [ 27.052397] R13: 0000000000000200 R14: 0000000000000000 R15: ffff88800a887040<br /> [ 27.052404] FS: 0000000000000000(0000) GS:ffff88808ca57000(0000) knlGS:0000000000000000<br /> [ 27.052408] CS: e030 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> [ 27.052412] CR2: 00007f9714004360 CR3: 0000000004834000 CR4: 0000000000050660<br /> [ 27.052418] Call Trace:<br /> [ 27.052420] <br /> [ 27.052422] xen_9pfs_front_changed+0x5d5/0x720<br /> [ 27.052426] ? xenbus_otherend_changed+0x72/0x140<br /> [ 27.052430] ? __pfx_xenwatch_thread+0x10/0x10<br /> [ 27.052434] xenwatch_thread+0x94/0x1c0<br /> [ 27.052438] ? __pfx_autoremove_wake_function+0x10/0x10<br /> [ 27.052442] kthread+0xf8/0x240<br /> [ 27.052445] ? __pfx_kthread+0x10/0x10<br /> [ 27.052449] ? __pfx_kthread+0x10/0x10<br /> [ 27.052452] ret_from_fork+0x16b/0x1a0<br /> [ 27.052456] ? __pfx_kthread+0x10/0x10<br /> [ 27.052459] ret_from_fork_asm+0x1a/0x30<br /> [ 27.052463] <br /> [ 27.052465] Modules linked in:<br /> [ 27.052471] ---[ end trace 0000000000000000 ]---

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net/sched: act_skbedit: fix divide-by-zero in tcf_skbedit_hash()<br /> <br /> Commit 38a6f0865796 ("net: sched: support hash selecting tx queue")<br /> added SKBEDIT_F_TXQ_SKBHASH support. The inclusive range size is<br /> computed as:<br /> <br /> mapping_mod = queue_mapping_max - queue_mapping + 1;<br /> <br /> The range size can be 65536 when the requested range covers all possible<br /> u16 queue IDs (e.g. queue_mapping=0 and queue_mapping_max=U16_MAX).<br /> That value cannot be represented in a u16 and previously wrapped to 0,<br /> so tcf_skbedit_hash() could trigger a divide-by-zero:<br /> <br /> queue_mapping += skb_get_hash(skb) % params-&gt;mapping_mod;<br /> <br /> Compute mapping_mod in a wider type and reject ranges larger than U16_MAX<br /> to prevent params-&gt;mapping_mod from becoming 0 and avoid the crash.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> x86/kexec: add a sanity check on previous kernel&amp;#39;s ima kexec buffer<br /> <br /> When the second-stage kernel is booted via kexec with a limiting command<br /> line such as "mem=", the physical range that contains the carried<br /> over IMA measurement list may fall outside the truncated RAM leading to a<br /> kernel panic.<br /> <br /> BUG: unable to handle page fault for address: ffff97793ff47000<br /> RIP: ima_restore_measurement_list+0xdc/0x45a<br /> #PF: error_code(0x0000) – not-present page<br /> <br /> Other architectures already validate the range with page_is_ram(), as done<br /> in commit cbf9c4b9617b ("of: check previous kernel&amp;#39;s ima-kexec-buffer<br /> against memory bounds") do a similar check on x86.<br /> <br /> Without carrying the measurement list across kexec, the attestation<br /> would fail.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ntb: ntb_hw_switchtec: Fix array-index-out-of-bounds access<br /> <br /> Number of MW LUTs depends on NTB configuration and can be set to MAX_MWS,<br /> This patch protects against invalid index out of bounds access to mw_sizes<br /> When invalid access print message to user that configuration is not valid.