In the Linux kernel, the following vulnerability has been resolved:
net/mlx5e: xsk: Fix unlocked writing to ICOSQ
During napi poll, when the affinity changes and there's still XSK work to be done, we trigger an ICOSQ interrupt on the new CPU. However, this triggering on the ICOSQ is done unprotected.
There are 2 such races:
A) mlx5e_trigger_irq() is called while mlx5e_xsk_alloc_rx_mpwqe() is running from a different CPU due to affinity change. This can happen because IRQ triggering is done after napi_complete_done(). At this point the NAPI can be scheduled on a different CPU. Like this:
CPU A (old affinity, NAPI tail) CPU B (new affinity, fresh NAPI) ------------------------------- -------------------------------- napi_complete_done() clears SCHED mlx5e_cq_arm(...) napi_schedule_prep() sets SCHED mlx5e_napi_poll() mlx5e_xsk_alloc_rx_mpwqe() mlx5e_icosq_sync_lock() // noop memcpy 640 B UMR body advance sq->pc by 10 mlx5e_trigger_irq(&c->icosq) wqe_info[pi] = {NOP, 1} mlx5e_post_nop() advances sq->pc
B) mlx5e_trigger_irq() is called on the ICOSQ when mlx5e_trigger_napi_icosq() is running.
The obvious fix would be to lock the ICOSQ. But ICOSQ has an optimized locking scheme that doesn't work for this scenario. Kick the async ICOSQ instead which is always locked.
This issue was noticed in the wild with the following splat:
netdevice: ge-0-0-1: Bad OP in ICOSQ CQE: 0xd WARNING: drivers/net/ethernet/mellanox/mlx5/core/en_rx.c:826 [...] [...] Call Trace: <IRQ> mlx5e_napi_poll+0x11d/0x7f0 [mlx5_core] __napi_poll+0x30/0x200 ? skb_defer_free_flush+0x9c/0xc0 net_rx_action+0x2fe/0x3f0 handle_softirqs+0xd8/0x340 __irq_exit_rcu+0xbc/0xe0 common_interrupt+0x85/0xa0 </IRQ> <TASK> asm_common_interrupt+0x26/0x40 [...] ---[ end trace 0000000000000000 ]--- mlx5_core 0000:08:00.0 ge-0-0-1: Error cqe on cqn 0x548, ci 0x2022, qn 0x8f4, opcode 0xd, syndrome 0x2, vendor syndrome 0x68 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00000030: 00 00 00 00 01 00 68 02 01 00 08 f4 de 14 59 d2 WQE DUMP: WQ size 16384 WQ cur size 0, WQE index 0x1e14, len: 64 00000000: 00 00 00 01 d9 ed 80 02 00 00 00 01 d9 ed 90 02 00000010: 00 00 00 01 d9 ed a0 02 00 00 00 01 d9 ed b0 02 00000020: 00 00 00 01 d9 ed c0 02 00 00 00 01 d9 ed d0 02 00000030: 00 00 00 01 d9 ed e0 02 00 00 00 01 d9 ed f0 02 mlx5_core 0000:08:00.0 ge-0-0-1: Error cqe on cqn 0x548, ci 0x2023, qn 0x8f4, opcode 0xd, syndrome 0x5, vendor syndrome 0xf9 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00000030: 00 00 00 00 01 00 f9 05 01 00 08 f4 de 15 cf d2
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Amazon_linux_2023 | — | Upgrade perf-debuginfoUpgrade kernel-modules-extra-commonUpgrade kernel-toolsUpgrade kernel-debuginfo-common-aarch64Upgrade bpftool-debuginfoUpgrade perfUpgrade bpftoolUpgrade kernel-livepatch-6.1.188-233.385Upgrade kernel-tools-debuginfoUpgrade kernel-debuginfo-common-x86_64Upgrade kernelUpgrade kernel-debuginfoUpgrade python3-perfUpgrade kernel-tools-develUpgrade kernel-modules-extraUpgrade python3-perf-debuginfoUpgrade kernel-develUpgrade kernel-headers | Oct 13, 2026 | Jul 24, 2026 |
| Debian | — | Upgrade linux-6.12Upgrade linux | Sep 30, 2026 | Jul 24, 2026 |
| Redhat_linux | — | No solution exists | Jul 30, 2026 | Jul 24, 2026 |
| Ubuntu | — | Upgrade linux-image-oracle-64k-7.0Upgrade linux-image-gcpUpgrade linux-image-7.0.0-1009-aws-64kUpgrade linux-image-7.0.0-1011-gcpUpgrade linux-image-nvidia-tegra-6.8Upgrade linux-image-7.0.0-1011-oracle-64kUpgrade linux-image-raspi-realtimeUpgrade linux-image-aws-64kUpgrade linux-image-gcp-7.0Upgrade linux-image-nvidia-tegra-rt-6.8Upgrade linux-image-nvidia-hwe-26.04Upgrade linux-image-raspi-7.0Upgrade linux-image-aws-7.0Upgrade linux-image-nvidia-64kUpgrade linux-image-nvidia-bos-7.0Upgrade linux-image-oracleUpgrade linux-image-7.0.0-2016-nvidia-bos-64kUpgrade linux-image-7.0.0-1015-raspi-realtimeUpgrade linux-image-7.0.0-1014-azureUpgrade linux-image-gcp-64k-7.0Upgrade linux-image-nvidia-64k-hwe-26.04Upgrade linux-image-6.8.0-1036-nvidia-tegraUpgrade linux-image-oracle-64kUpgrade linux-image-nvidiaUpgrade linux-image-raspiUpgrade linux-image-7.0.0-1016-nvidia-64kUpgrade linux-image-nvidia-bos-64k-7.0Upgrade linux-image-azureUpgrade linux-image-nvidia-tegraUpgrade linux-image-7.0.0-1009-awsUpgrade linux-image-nvidia-7.0Upgrade linux-image-7.0.0-1011-gcp-64kUpgrade linux-image-oracle-7.0Upgrade linux-image-7.0.0-1016-nvidiaUpgrade linux-image-7.0.0-1015-raspiUpgrade linux-image-raspi-realtime-7.0Upgrade linux-image-7.0.0-2016-nvidia-bosUpgrade linux-image-nvidia-64k-7.0Upgrade linux-image-nvidia-bos-64kUpgrade linux-image-azure-7.0Upgrade linux-image-awsUpgrade linux-image-nvidia-bosUpgrade linux-image-7.0.0-1011-oracleUpgrade linux-image-nvidia-tegra-rtUpgrade linux-image-aws-64k-7.0Upgrade linux-image-gcp-64kUpgrade linux-image-6.8.0-1036-nvidia-tegra-rt | Jul 28, 2026 | Jul 28, 2026 |
| Vmware Photon_os | — | Use 'tdnf update' to upgrade all packages to the latest version. | Sep 30, 2026 | Jul 24, 2026 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub