CVE-2025-40104: ixgbevf: fix mailbox API compatibility by negotiating supported features

Published Oct 30, 2025
·
Updated

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.

Affected Software

3 affected componentsFixes available
Intel Linux kernel
Microsoft azl3 kernel 6.6.104.2-4
Microsoft azl3 kernel 6.6.112.1-2

Event History

Oct 30, 2025
CVE Published
via MITRE·09:48 AM
Data Sourced
via MITRE·09:48 AM
DescriptionSeverity
Data Sourced
via NVD·10:15 AM
DescriptionSeverity
Oct 31, 2025
Data Sourced
via Microsoft·01:09 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·01:09 AM
Affected Software
Updated
via Microsoft·01:09 AM
DescriptionSeverity

Frequently Asked Questions

1

What is the severity of CVE-2025-40104?

The severity of CVE-2025-40104 is classified as moderate, indicating potential impact on systems using affected drivers.

2

How do I fix CVE-2025-40104?

To fix CVE-2025-40104, update the Linux kernel to the latest version from Intel that includes the mailbox API compatibility fix.

3

What systems are affected by CVE-2025-40104?

CVE-2025-40104 affects systems running the Intel Linux kernel that utilize certain 10G adapter drivers.

4

What is the nature of the vulnerability for CVE-2025-40104?

CVE-2025-40104 involves backward compatibility issues in the mailbox API related to 10G network adapters.

5

Is there a patch available for CVE-2025-40104?

Yes, a patch is available in the updated Linux kernel that addresses the compatibility issues introduced with the mailbox API.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203