Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: mac80211: ocb: skip rx_no_sta when interface is not joined<br /> <br /> ieee80211_ocb_rx_no_sta() assumes a valid channel context, which is only<br /> present after JOIN_OCB.<br /> <br /> RX may run before JOIN_OCB is executed, in which case the OCB interface<br /> is not operational. Skip RX peer handling when the interface is not<br /> joined to avoid warnings in the RX path.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> smb/server: fix refcount leak in smb2_open()<br /> <br /> When ksmbd_vfs_getattr() fails, the reference count of ksmbd_file<br /> must be released.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> smb/server: fix refcount leak in parse_durable_handle_context()<br /> <br /> When the command is a replay operation and -ENOEXEC is returned,<br /> the refcount of ksmbd_file must be released.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> riscv: Sanitize syscall table indexing under speculation<br /> <br /> The syscall number is a user-controlled value used to index into the<br /> syscall table. Use array_index_nospec() to clamp this value after the<br /> bounds check to prevent speculative out-of-bounds access and subsequent<br /> data leakage via cache side channels.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> dmaengine: mmp_pdma: Fix race condition in mmp_pdma_residue()<br /> <br /> Add proper locking in mmp_pdma_residue() to prevent use-after-free when<br /> accessing descriptor list and descriptor contents.<br /> <br /> The race occurs when multiple threads call tx_status() while the tasklet<br /> on another CPU is freeing completed descriptors:<br /> <br /> CPU 0 CPU 1<br /> ----- -----<br /> mmp_pdma_tx_status()<br /> mmp_pdma_residue()<br /> -&gt; NO LOCK held<br /> list_for_each_entry(sw, ..)<br /> DMA interrupt<br /> dma_do_tasklet()<br /> -&gt; spin_lock(&amp;desc_lock)<br /> list_move(sw-&gt;node, ...)<br /> spin_unlock(&amp;desc_lock)<br /> | dma_pool_free(sw) access sw-&gt;desc 1).<br /> <br /> Fix by protecting the chain_running list iteration and descriptor access<br /> with the chan-&gt;desc_lock spinlock.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: wlcore: ensure skb headroom before skb_push<br /> <br /> This avoids occasional skb_under_panic Oops from wl1271_tx_work. In this case, headroom is<br /> less than needed (typically 110 - 94 = 16 bytes).

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> smb/server: call ksmbd_session_rpc_close() on error path in create_smb2_pipe()<br /> <br /> When ksmbd_iov_pin_rsp() fails, we should call ksmbd_session_rpc_close().

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net/mlx5e: TC, delete flows only for existing peers<br /> <br /> When deleting TC steering flows, iterate only over actual devcom<br /> peers instead of assuming all possible ports exist. This avoids<br /> touching non-existent peers and ensures cleanup is limited to<br /> devices the driver is currently connected to.<br /> <br /> BUG: kernel NULL pointer dereference, address: 0000000000000008<br /> #PF: supervisor write access in kernel mode<br /> #PF: error_code(0x0002) - not-present page<br /> PGD 133c8a067 P4D 0<br /> Oops: Oops: 0002 [#1] SMP<br /> CPU: 19 UID: 0 PID: 2169 Comm: tc Not tainted 6.18.0+ #156 NONE<br /> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014<br /> RIP: 0010:mlx5e_tc_del_fdb_peers_flow+0xbe/0x200 [mlx5_core]<br /> Code: 00 00 a8 08 74 a8 49 8b 46 18 f6 c4 02 74 9f 4c 8d bf a0 12 00 00 4c 89 ff e8 0e e7 96 e1 49 8b 44 24 08 49 8b 0c 24 4c 89 ff 89 41 08 48 89 08 49 89 2c 24 49 89 5c 24 08 e8 7d ce 96 e1 49<br /> RSP: 0018:ff11000143867528 EFLAGS: 00010246<br /> RAX: 0000000000000000 RBX: dead000000000122 RCX: 0000000000000000<br /> RDX: ff11000143691580 RSI: ff110001026e5000 RDI: ff11000106f3d2a0<br /> RBP: dead000000000100 R08: 00000000000003fd R09: 0000000000000002<br /> R10: ff11000101c75690 R11: ff1100085faea178 R12: ff11000115f0ae78<br /> R13: 0000000000000000 R14: ff11000115f0a800 R15: ff11000106f3d2a0<br /> FS: 00007f35236bf740(0000) GS:ff110008dc809000(0000) knlGS:0000000000000000<br /> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> CR2: 0000000000000008 CR3: 0000000157a01001 CR4: 0000000000373eb0<br /> Call Trace:<br /> <br /> mlx5e_tc_del_flow+0x46/0x270 [mlx5_core]<br /> mlx5e_flow_put+0x25/0x50 [mlx5_core]<br /> mlx5e_delete_flower+0x2a6/0x3e0 [mlx5_core]<br /> tc_setup_cb_reoffload+0x20/0x80<br /> fl_reoffload+0x26f/0x2f0 [cls_flower]<br /> ? mlx5e_tc_reoffload_flows_work+0xc0/0xc0 [mlx5_core]<br /> ? mlx5e_tc_reoffload_flows_work+0xc0/0xc0 [mlx5_core]<br /> tcf_block_playback_offloads+0x9e/0x1c0<br /> tcf_block_unbind+0x7b/0xd0<br /> tcf_block_setup+0x186/0x1d0<br /> tcf_block_offload_cmd.isra.0+0xef/0x130<br /> tcf_block_offload_unbind+0x43/0x70<br /> __tcf_block_put+0x85/0x160<br /> ingress_destroy+0x32/0x110 [sch_ingress]<br /> __qdisc_destroy+0x44/0x100<br /> qdisc_graft+0x22b/0x610<br /> tc_get_qdisc+0x183/0x4d0<br /> rtnetlink_rcv_msg+0x2d7/0x3d0<br /> ? rtnl_calcit.isra.0+0x100/0x100<br /> netlink_rcv_skb+0x53/0x100<br /> netlink_unicast+0x249/0x320<br /> ? __alloc_skb+0x102/0x1f0<br /> netlink_sendmsg+0x1e3/0x420<br /> __sock_sendmsg+0x38/0x60<br /> ____sys_sendmsg+0x1ef/0x230<br /> ? copy_msghdr_from_user+0x6c/0xa0<br /> ___sys_sendmsg+0x7f/0xc0<br /> ? ___sys_recvmsg+0x8a/0xc0<br /> ? __sys_sendto+0x119/0x180<br /> __sys_sendmsg+0x61/0xb0<br /> do_syscall_64+0x55/0x640<br /> entry_SYSCALL_64_after_hwframe+0x4b/0x53<br /> RIP: 0033:0x7f35238bb764<br /> Code: 15 b9 86 0c 00 f7 d8 64 89 02 b8 ff ff ff ff eb bf 0f 1f 44 00 00 f3 0f 1e fa 80 3d e5 08 0d 00 00 74 13 b8 2e 00 00 00 0f 05 3d 00 f0 ff ff 77 4c c3 0f 1f 00 55 48 89 e5 48 83 ec 20 89 55<br /> RSP: 002b:00007ffed4c35638 EFLAGS: 00000202 ORIG_RAX: 000000000000002e<br /> RAX: ffffffffffffffda RBX: 000055a2efcc75e0 RCX: 00007f35238bb764<br /> RDX: 0000000000000000 RSI: 00007ffed4c356a0 RDI: 0000000000000003<br /> RBP: 00007ffed4c35710 R08: 0000000000000010 R09: 00007f3523984b20<br /> R10: 0000000000000004 R11: 0000000000000202 R12: 00007ffed4c35790<br /> R13: 000000006947df8f R14: 000055a2efcc75e0 R15: 00007ffed4c35780

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: wwan: t7xx: fix potential skb-&gt;frags overflow in RX path<br /> <br /> When receiving data in the DPMAIF RX path,<br /> the t7xx_dpmaif_set_frag_to_skb() function adds<br /> page fragments to an skb without checking if the number of<br /> fragments has exceeded MAX_SKB_FRAGS. This could lead to a buffer overflow<br /> in skb_shinfo(skb)-&gt;frags[] array, corrupting adjacent memory and<br /> potentially causing kernel crashes or other undefined behavior.<br /> <br /> This issue was identified through static code analysis by comparing with a<br /> similar vulnerability fixed in the mt76 driver commit b102f0c522cf ("mt76:<br /> fix array overflow on receiving too many fragments for a packet").<br /> <br /> The vulnerability could be triggered if the modem firmware sends packets<br /> with excessive fragments. While under normal protocol conditions (MTU 3080<br /> bytes, BAT buffer 3584 bytes),<br /> a single packet should not require additional<br /> fragments, the kernel should not blindly trust firmware behavior.<br /> Malicious, buggy, or compromised firmware could potentially craft packets<br /> with more fragments than the kernel expects.<br /> <br /> Fix this by adding a bounds check before calling skb_add_rx_frag() to<br /> ensure nr_frags does not exceed MAX_SKB_FRAGS.<br /> <br /> The check must be performed before unmapping to avoid a page leak<br /> and double DMA unmap during device teardown.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> bonding: fix use-after-free due to enslave fail after slave array update<br /> <br /> Fix a use-after-free which happens due to enslave failure after the new<br /> slave has been added to the array. Since the new slave can be used for Tx<br /> immediately, we can use it after it has been freed by the enslave error<br /> cleanup path which frees the allocated slave memory. Slave update array is<br /> supposed to be called last when further enslave failures are not expected.<br /> Move it after xdp setup to avoid any problems.<br /> <br /> It is very easy to reproduce the problem with a simple xdp_pass prog:<br /> ip l add bond1 type bond mode balance-xor<br /> ip l set bond1 up<br /> ip l set dev bond1 xdp object xdp_pass.o sec xdp_pass<br /> ip l add dumdum type dummy<br /> <br /> Then run in parallel:<br /> while :; do ip l set dumdum master bond1 1&gt;/dev/null 2&gt;&amp;1; done;<br /> mausezahn bond1 -a own -b rand -A rand -B 1.1.1.1 -c 0 -t tcp "dp=1-1023, flags=syn"<br /> <br /> The crash happens almost immediately:<br /> [ 605.602850] Oops: general protection fault, probably for non-canonical address 0xe0e6fc2460000137: 0000 [#1] SMP KASAN NOPTI<br /> [ 605.602916] KASAN: maybe wild-memory-access in range [0x07380123000009b8-0x07380123000009bf]<br /> [ 605.602946] CPU: 0 UID: 0 PID: 2445 Comm: mausezahn Kdump: loaded Tainted: G B 6.19.0-rc6+ #21 PREEMPT(voluntary)<br /> [ 605.602979] Tainted: [B]=BAD_PAGE<br /> [ 605.602998] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014<br /> [ 605.603032] RIP: 0010:netdev_core_pick_tx+0xcd/0x210<br /> [ 605.603063] Code: 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 3e 01 00 00 48 b8 00 00 00 00 00 fc ff df 4c 8b 6b 08 49 8d 7d 30 48 89 fa 48 c1 ea 03 3c 02 00 0f 85 25 01 00 00 49 8b 45 30 4c 89 e2 48 89 ee 48 89<br /> [ 605.603111] RSP: 0018:ffff88817b9af348 EFLAGS: 00010213<br /> [ 605.603145] RAX: dffffc0000000000 RBX: ffff88817d28b420 RCX: 0000000000000000<br /> [ 605.603172] RDX: 00e7002460000137 RSI: 0000000000000008 RDI: 07380123000009be<br /> [ 605.603199] RBP: ffff88817b541a00 R08: 0000000000000001 R09: fffffbfff3ed8c0c<br /> [ 605.603226] R10: ffffffff9f6c6067 R11: 0000000000000001 R12: 0000000000000000<br /> [ 605.603253] R13: 073801230000098e R14: ffff88817d28b448 R15: ffff88817b541a84<br /> [ 605.603286] FS: 00007f6570ef67c0(0000) GS:ffff888221dfa000(0000) knlGS:0000000000000000<br /> [ 605.603319] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> [ 605.603343] CR2: 00007f65712fae40 CR3: 000000011371b000 CR4: 0000000000350ef0<br /> [ 605.603373] Call Trace:<br /> [ 605.603392] <br /> [ 605.603410] __dev_queue_xmit+0x448/0x32a0<br /> [ 605.603434] ? __pfx_vprintk_emit+0x10/0x10<br /> [ 605.603461] ? __pfx_vprintk_emit+0x10/0x10<br /> [ 605.603484] ? __pfx___dev_queue_xmit+0x10/0x10<br /> [ 605.603507] ? bond_start_xmit+0xbfb/0xc20 [bonding]<br /> [ 605.603546] ? _printk+0xcb/0x100<br /> [ 605.603566] ? __pfx__printk+0x10/0x10<br /> [ 605.603589] ? bond_start_xmit+0xbfb/0xc20 [bonding]<br /> [ 605.603627] ? add_taint+0x5e/0x70<br /> [ 605.603648] ? add_taint+0x2a/0x70<br /> [ 605.603670] ? end_report.cold+0x51/0x75<br /> [ 605.603693] ? bond_start_xmit+0xbfb/0xc20 [bonding]<br /> [ 605.603731] bond_start_xmit+0x623/0xc20 [bonding]

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/imx/tve: fix probe device leak<br /> <br /> Make sure to drop the reference taken to the DDC device during probe on<br /> probe failure (e.g. probe deferral) and on driver unbind.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> mptcp: fix race in mptcp_pm_nl_flush_addrs_doit()<br /> <br /> syzbot and Eulgyu Kim reported crashes in mptcp_pm_nl_get_local_id()<br /> and/or mptcp_pm_nl_is_backup()<br /> <br /> Root cause is list_splice_init() in mptcp_pm_nl_flush_addrs_doit()<br /> which is not RCU ready.<br /> <br /> list_splice_init_rcu() can not be called here while holding pernet-&gt;lock<br /> spinlock.<br /> <br /> Many thanks to Eulgyu Kim for providing a repro and testing our patches.