Skip to main content

Linux Kernel ixgbevf CVE-2025-40104

HIGH
2025-10-30 416baaa9-dc9f-4396-8d5f-8c081fb06d67
7.8
CVSS 3.1 · Vendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Share

Severity by source

Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
5.5 MEDIUM

Description and tag indicate a local driver crash (availability only) with no confidentiality/integrity impact; requires local driver load/config so PR:L, no user interaction.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
0.0 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:N
Red Hat
5.5 MEDIUM
qualitative

Primary rating from Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67).

CVSS VectorVendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Analysis Generated
Jul 30, 2026 - 07:39 vuln.today
CVE Published
Oct 30, 2025 - 10:15 cve.org
HIGH 7.8

DescriptionCVE.org

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.

AnalysisAI

Local denial-of-service in the Linux kernel's ixgbevf driver (Intel 10G SR-IOV virtual function driver) arises from broken mailbox API negotiation between PF and VF drivers. Since API 1.4/1.5/1.6, VF-specific features (IPsec offload, ESX enhanced mailbox) were bolted on without a feature-negotiation mechanism, causing crashes when the VF driver assumes support the underlying PF/kernel ixgbe driver does not actually implement. The fix introduces a new mailbox op so the VF queries the PF for supported features before enabling IPsec or ESX-specific paths. No public exploit identified at time of analysis; EPSS is low (0.19%, 9th percentile) and there is no KEV listing.

Technical ContextAI

The affected component is ixgbevf, the Linux virtual-function driver for Intel 82599/X540/X550-class 10 Gigabit SR-IOV network adapters. VF and PF drivers communicate over a hardware mailbox with a versioned API. Backward compatibility was historically preserved across driver families (Linux ixgbe, ESX, out-of-tree), but commit 0062e7cc955e (API 1.4, VF IPsec offload) and commit 339f28964147 (API 1.5, new PF/VF mailbox) added features tied to specific PF implementations without any way to negotiate whether the peer supports them. API 1.6 code paths crash the Linux ixgbe driver outright. Jake's earlier commit d0725312adf5 mitigated the IPsec case by disabling IPsec on API 1.5, but that regressed IPsec support and, after bumping to 1.6, broke ESX mailbox support. The root cause is a protocol/version-negotiation defect (no assigned CWE in the input; conceptually a compatibility/assumption fault leading to a crash). The fix adds a feature-negotiation mailbox op, extensible for future features.

Affected ProductsAI

The Linux kernel ixgbevf driver (Intel 10G SR-IOV virtual function driver for 82599/X540/X550-family adapters) is affected across the kernel versions carrying the mailbox API 1.4 through 1.6 changes (commits 0062e7cc955e, 339f28964147). No CPE strings or exact affected version ranges were supplied in the input; affected versions must be inferred from the referenced stable-tree fix commits at git.kernel.org (2e0aab9ddaf1, 871ac1cd4ce4, a376e29b1b19, a7075f501bd3, bf580112ed61), which indicate the fix was backported to multiple stable branches. There is no vendor advisory URL beyond the kernel.org git references.

RemediationAI

Upstream fix available (PR/commit); released patched version not independently confirmed - apply the kernel update containing the ixgbevf feature-negotiation commits referenced at git.kernel.org (2e0aab9ddaf1428602c78f12064cd1e6ffcc4d18, 871ac1cd4ce4804defcb428cbb003fd84c415ff4, a376e29b1b196dc90b50df7e5e3947e3026300c4, a7075f501bd33c93570af759b6f4302ef0175168, bf580112ed61736c2645a893413a04732505d4b1), i.e. upgrade to the stable kernel release that includes these backports for your branch. As a compensating control before patching, avoid mixing VF drivers against PF drivers advertising incompatible mailbox API versions (1.5/1.6), and where feasible disable/avoid VF IPsec offload on affected combinations (the pre-fix behavior already stops IPsec on API 1.5, at the cost of losing IPsec offload); for pure Linux ixgbe PF + ixgbevf VF deployments, keeping driver versions in sync avoids the crash. Trade-off: disabling IPsec offload reduces crypto throughput/offload benefit but restores stability.

More in Intel

View all
CVE-2021-44228 CRITICAL POC
10.0 Dec 10

Apache Log4j2 contains a critical JNDI injection vulnerability known as 'Log4Shell' that allows unauthenticated remote c

CVE-2017-5689 CRITICAL POC
9.8 May 02

An unprivileged network attacker could gain system privileges to provisioned Intel manageability SKUs: Intel Active Mana

CVE-2012-5958 CRITICAL POC
10.0 Jan 31

Stack-based buffer overflow in the unique_service_name function in ssdp/ssdp_server.c in the SSDP parser in the portable

CVE-2012-0217 HIGH POC
7.2 Jun 12

The x86-64 kernel system-call functionality in Xen 4.1.2 and earlier, as used in Citrix XenServer 6.0.2 and earlier and

CVE-2012-5959 CRITICAL POC
10.0 Jan 31

Stack-based buffer overflow in the unique_service_name function in ssdp/ssdp_server.c in the SSDP parser in the portable

CVE-2012-5964 CRITICAL POC
10.0 Jan 31

Stack-based buffer overflow in the unique_service_name function in ssdp/ssdp_server.c in the SSDP parser in the portable

CVE-2012-5963 CRITICAL POC
10.0 Jan 31

Stack-based buffer overflow in the unique_service_name function in ssdp/ssdp_server.c in the SSDP parser in the portable

CVE-2012-5961 CRITICAL POC
10.0 Jan 31

Stack-based buffer overflow in the unique_service_name function in ssdp/ssdp_server.c in the SSDP parser in the portable

CVE-2017-5753 MEDIUM POC
5.6 Jan 04

Systems with microprocessors utilizing speculative execution and branch prediction may allow unauthorized disclosure of

CVE-2012-5965 CRITICAL POC
10.0 Jan 31

Stack-based buffer overflow in the unique_service_name function in ssdp/ssdp_server.c in the SSDP parser in the portable

CVE-2012-5962 CRITICAL POC
10.0 Jan 31

Stack-based buffer overflow in the unique_service_name function in ssdp/ssdp_server.c in the SSDP parser in the portable

CVE-2012-5960 CRITICAL POC
10.0 Jan 31

Stack-based buffer overflow in the unique_service_name function in ssdp/ssdp_server.c in the SSDP parser in the portable

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
Container suse/sl-micro/6.0/baremetal-os-container:latest Container suse/sl-micro/6.0/kvm-os-container:latest Container suse/sl-micro/6.0/rt-os-container:latest Container suse/sl-micro/6.0/toolbox:latest Affected
Container suse/sl-micro/6.0/base-os-container:latest Image SLE-Micro Image SLE-Micro-Azure Image SLE-Micro-BYOS Image SLE-Micro-BYOS-Azure Image SLE-Micro-BYOS-EC2 Image SLE-Micro-BYOS-GCE Image SLE-Micro-EC2 Image SLE-Micro-GCE Affected
Image SL-Micro-Default Image SL-Micro-Default-SelfInstall Image SL-Micro-Default-encrypted Image SL-Micro-Default-qcow Image SUSE-Multi-Linux-Manager-Server-EC2-llc Image SUSE-Multi-Linux-Manager-Server-EC2-ltd Affected
Image SLES-Azure-3P Image SLES-Azure-Basic Image SLES-Azure-Standard Image SLES-BYOS-Azure Image SLES-BYOS-EC2 Image SLES-BYOS-GCE Image SLES-CHOST-BYOS-Aliyun Image SLES-CHOST-BYOS-Azure Image SLES-CHOST-BYOS-EC2 Image SLES-CHOST-BYOS-GCE Image SLES-CHOST-BYOS-GDC Image SLES-CHOST-BYOS-SAP-CCloud Image SLES-EC2 Image SLES-EC2-ECS Image SLES-GCE Image SLES-GCE-3P Image SLES-Hardened-BYOS-Azure Image SLES-Hardened-BYOS-EC2 Image SLES-Hardened-BYOS-GCE Image SLES-SAPCAL-Azure Image SLES-SAPCAL-EC2 Image SLES-SAPCAL-GCE Affected
Image SLES-SAP-Azure Image SLES-SAP-Azure-3P Image SLES-SAP-BYOS-Azure Image SLES-SAP-BYOS-EC2 Image SLES-SAP-BYOS-GCE Image SLES-SAP-EC2 Image SLES-SAP-GCE Image SLES-SAP-GCE-3P Affected

Share

CVE-2025-40104 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy