Skip to content
Heist/ feed
Back to feed
HighFix available

ixgbevf: fix mailbox API compatibility by negotiating supported features

Type: advisorySources: OSV

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 dr

Products
Kernel
Affected versions
Not specified
Fixed versions
6.1.158, 6.12.55, 6.17.5, 6.6.114
CVEs
CVE-2025-40104
Confirmed fixed CVEs
Not specified
Updated in this feed
4 Nov 2026, 03:53 UTC · Revision 1

Source evidence

ixgbevf: fix mailbox API compatibility by negotiating supported features

core-osv · Original source

Published 30 Oct 2025, 09:48 UTC

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 dr

osv:CVE-2025-40104

Kernel

Fixed versions: 6.1.158, 6.6.114, 6.12.55, 6.17.5

Complete source record
{
  "id": "9b634f199667462ecd2bd7595fc8ba278232e241bd318e968c81865ddfe8d0bf",
  "url": "https://osv.dev/vulnerability/CVE-2025-40104",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "ixgbevf: fix mailbox API compatibility by negotiating supported features",
    "summary": "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 dr",
    "evidence": "osv:CVE-2025-40104",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.1.158",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.6.114",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.12.55",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.17.5",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "high",
    "structured": {
      "id": "CVE-2025-40104",
      "aliases": [
        "CVE-2025-40104"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "0062e7cc955e0827a88570ed36ea511a7dcb391e"
                },
                {
                  "fixed": "871ac1cd4ce4804defcb428cbb003fd84c415ff4"
                },
                {
                  "fixed": "2e0aab9ddaf1428602c78f12064cd1e6ffcc4d18"
                },
                {
                  "fixed": "bf580112ed61736c2645a893413a04732505d4b1"
                },
                {
                  "fixed": "a376e29b1b196dc90b50df7e5e3947e3026300c4"
                },
                {
                  "fixed": "a7075f501bd33c93570af759b6f4302ef0175168"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-40104.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "4.20.0"
                },
                {
                  "fixed": "6.1.158"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.2.0"
                },
                {
                  "fixed": "6.6.114"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.7.0"
                },
                {
                  "fixed": "6.12.55"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.13.0"
                },
                {
                  "fixed": "6.17.5"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-40104.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:32.998487819Z",
      "provider": "osv",
      "references": [
        "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",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/40xxx/CVE-2025-40104.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2025-40104",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/40xxx/CVE-2025-40104.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2025-40104",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 500173,
  "published_at": "2025-10-30T09:48:09.051+00:00"
}