CVE-2025-40104

In the Linux kernel, the following vulnerability has been resolved: ixgbevf: fix mailbox API compatibility by negotiating supported features There was backward compatibility in the terms of mailbox API. Various drivers from various OSes supporting 10G adapters from Intel portfolio could easily negotiate mailbox API. This convention has been broken since introducing API 1.4. Commit 0062e7cc955e ("ixgbevf: add VF IPsec offload code") added support for IPSec which is specific only for the kernel ixgbe driver. None of the rest of the Intel 10G PF/VF drivers supports it. And actually lack of support was not included in the IPSec implementation - there were no such code paths. No possibility to negotiate support for the feature was introduced along with introduction of the feature itself. Commit 339f28964147 ("ixgbevf: Add support for new mailbox communication between PF and VF") increasing API version to 1.5 did the same - it introduced code supported specifically by the PF ESX driver. It altered API version for the VF driver in the same time not touching the version defined for the PF ixgbe driver. It led to additional discrepancies, as the code provided within API 1.6 cannot be supported for Linux ixgbe driver as it causes crashes. The issue was noticed some time ago and mitigated by Jake within the commit d0725312adf5 ("ixgbevf: stop attempting IPSEC offload on Mailbox API 1.5"). As a result we have regression for IPsec support and after increasing API to version 1.6 ixgbevf driver stopped to support ESX MBX. To fix this mess add new mailbox op asking PF driver about supported features. Basing on a response determine whether to set support for IPSec and ESX-specific enhanced mailbox. New mailbox op, for compatibility purposes, must be added within new API revision, as API version of OOT PF & VF drivers is already increased to 1.6 and doesn't incorporate features negotiate op. Features negotiation mechanism gives possibility to be extended with new features when needed in the future.

• https://git.kernel.org/stable/c/2e0aab9ddaf1428602c78f12064cd1e6ffcc4d18
• https://git.kernel.org/stable/c/871ac1cd4ce4804defcb428cbb003fd84c415ff4
• https://git.kernel.org/stable/c/a376e29b1b196dc90b50df7e5e3947e3026300c4
• https://git.kernel.org/stable/c/a7075f501bd33c93570af759b6f4302ef0175168
• https://git.kernel.org/stable/c/bf580112ed61736c2645a893413a04732505d4b1

Published

Oct 30, 2025

Last Modified

Jul 30, 2026

Status

Deferred

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2025-40099In the Linux kernel, the following vulnerability has been re…9.4
• CVE-2025-4010The Netcom NTC 6200 and NWL 222 series expose a web interfac…8.6
• CVE-2025-40100In the Linux kernel, the following vulnerability has been re…
• CVE-2025-40101In the Linux kernel, the following vulnerability has been re…
• CVE-2025-40102In the Linux kernel, the following vulnerability has been re…
• CVE-2025-40103In the Linux kernel, the following vulnerability has been re…
• CVE-2025-40105In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2025-40106In the Linux kernel, the following vulnerability has been re…
• CVE-2025-40107In the Linux kernel, the following vulnerability has been re…
• CVE-2025-40108In the Linux kernel, the following vulnerability has been re…
• CVE-2025-40109In the Linux kernel, the following vulnerability has been re…
• CVE-2025-4011A vulnerability has been found in Redmine 6.0.0/6.0.1/6.0.2/…5.1